Misleading error message when failing to find constructor.

Consider

var sql = "select [TABLE_CATALOG] as [TableCatalog], [TABLE_SCHEMA] as [TableSchema], [TABLE_NAME] as [TableName], [COLUMN_NAME] as [ColumnName], [IS_NULLABLE] as [IsNullable], [DATA_TYPE] as [DataType], [CHARACTER_MAXIMUM_LENGTH] as [CharacterMaximumLength], [NUMERIC_PRECISION_RADIX] as [NumericPrecisionRadix], [NUMERIC_PRECISION] as [NumericPrecision] from INFORMATION_SCHEMA.COLUMNS";

public record Column(
        string TableCatalog, 
        string TableSchema, 
        string TableName,
        string ColumnName,
        string IsNullable,
        int DataType, // WRONG
        int? CharacterMaximumLength, // CORRECT
        short? NumericPrecisionRadix,
        byte? NumericPrecision);

var x = await connection.QueryAsync<Column>(sql);

Then the error message generated is

A parameterless default constructor or one matching signature (System.String TableCatalog, System.String TableSchema, System.String TableName, System.String ColumnName, System.String IsNullable, System.String DataType, System.Int32 CharacterMaximumLength, System.Int16 NumericPrecisionRadix, System.Byte NumericPrecision) is required for ConsoleApp4.Column materialization

Note that it suggests we need to change the last three fields, but in practice you only need to fix DataType.

Reproduce the issue with the shown QueryAsync call and the mismatched DataType constructor parameter. Trace the constructor-matching and materialization error generation, then verify that the message identifies the actual mismatched parameter and that the example has regression coverage.