First attempt at fixing unicode inserts into varchars

Bump version to 1.46_1
change to look at bound data before selecting a bind type - if unicode,
use SQL_Wxxx no matter what SQLDescribeParam says
Add massive warning and explanation to the start of the pod about what
is changing and why
loads of other smaller pod changes
minor rewording to changes for last change
fix typos in warning and minor wording changes
add 45_unicode_varchar.t test

MS SQL Server only test right now - will expand in the future
hard wire table collation for now
add code to output server, database, column collations
better testing of unicode and non unicode in varchars - still WIP
new faq for supposedly retrieving garbled data
clarify and advice on use of types on bind_param
better test - mix codepage and unicode inserts
cope with changing unicode/codepage strings in successive binds
fix "Unable to fetch information about the error" state from IM008 to HY000
wrong skip count
cope with not having Win32::API::More

cope with not having Win32::API::More
skip tests better when stuff not available
small catalog/schema usage fix + edge case for new unicode support

MSAccess does not support schemas and newish change to table_info broke
that.
Edge case for new unicode support where SQLDescribeParam failed
schema/catalog not supported issue in table_info plus new unicode support edge case

MSAccess does not support schemas - new table_info expects schema
support - check at connect time
edge case for new unicode support - when SQLDescribeParam fails
new randon links - common unicode problems
wrong type in trace msg
typo