Fix invalid precision error

[MichaelSun90]

Fix for issue #1491

[MichaelSun90]

Upon discuses, we decide to not do the SQL data type reset step within bind params function that initially there for fixing #1448. With that change, the find_param return a param with SQL unknow data type when execute the prepared query for the second time which will later be process into a SQL wvarchar type. When the logic try to bind the wvarchar with the input 8000 size which is twice the max size for a wvarchar type can hold cause the invalid precision error. This type process is related to a older version of utf8 encoding handling. The varchar type able to hold utf8 and utf16 encoding for newer version SQL server (later then 2019), and the handling for this and backward compatibility may come in a later. If the logic does not reset the SQL type unknow, the find_param will return the stored datatype varchar, and 8000 size will no longer be a problem. For the issue #1448, if user properly handles the input param data, then the current logic should handles the task without a problem. Also, the error :"Invalid character value for cast specification" returned for that issue seems properly informed the user the cause for the error.