different collations fix

[dilshatm]

Required for all PRs:

• Signed CLA.
• Associated README.md updated.
• Has appropriate unit tests.

[danielnelson]

@m82labs Any chance we would need something similar on the v2 query type?

[m82labs]

I would need to better understand what the reasoning was for adding this. @dilshatm what was the reason for this change, what errors were you seeing?

[dilshatm]

Collation of the database in connectionstring is Cyrillic_General_CI_AS. Collation of tempdb is SQL_Latin1_General_CP1_CI_AS.

For example, running sqlWaitStatsCategorized in first database caused 2 error message

Msg 468, Level 16, State 9, Line 270
Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Msg 468, Level 16, State 9, Line 286
Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

For version2 itsn't actual, because there is no use of #temp tables.