fixup! Handle dialects supporting huge length limited strings

Use factory instead of creating new instance

Author: fredericDelaporte

src/NHibernate.Test/Async/NHSpecificTest/NH2302/Fixture.cs

@@ -53,7 +53,7 @@ public async Task StringHugeLengthAsync()
 			if (Sfi.ConnectionProvider.Driver is OdbcDriver || Dialect is MsSqlCeDialect)
 				Assert.Ignore("NH-4065, not fixed for Odbc and MsSqlCe");
 
-			if (Dialect.GetTypeName(new StringSqlType(10000)) != Dialect.GetLongestTypeName(DbType.String))
+			if (Dialect.GetTypeName(SqlTypeFactory.GetString(10000)) != Dialect.GetLongestTypeName(DbType.String))
 				Assert.Ignore("Current dialect does support limited strings of 10 000 characters");
 
             int id;

src/NHibernate.Test/NHSpecificTest/NH2302/Fixture.cs

@@ -42,7 +42,7 @@ public void StringHugeLength()
 			if (Sfi.ConnectionProvider.Driver is OdbcDriver || Dialect is MsSqlCeDialect)
 				Assert.Ignore("NH-4065, not fixed for Odbc and MsSqlCe");
 
-			if (Dialect.GetTypeName(new StringSqlType(10000)) != Dialect.GetLongestTypeName(DbType.String))
+			if (Dialect.GetTypeName(SqlTypeFactory.GetString(10000)) != Dialect.GetLongestTypeName(DbType.String))
 				Assert.Ignore("Current dialect does support limited strings of 10 000 characters");
 
             int id;