Support multi-catalog deployments

[tmasternak]

Version 3 of SqlTransprort supports only multi-schema setup. It should be possible to add multi-catalog support as well.

See #139 for more details
Inception: https://github.com/Particular/CustomerSuccess/issues/166

[mauroservienti]

As discussed this morning the catalog name should be part of the endpoint address as it is for the schema name in 3.0

[ramonsmits]

Should support both: userdb.dbo and also [userdb].[dbo] to also supports dots in catalogs and/or schemas.

[SzymonPobiega]

I am not convinced here. Single even SQL 2016 does not support cross-catalog transactions in AlwaysOn mode, catalog seems to be something physical rather than logical. I'd rather put the catalog/database in same bucket as SQL server instances and handle it similarly to RabbitMQ shovel plugin.

[mauroservienti]

@SzymonPobiega here you are sir #146

And you have a good point, @tmasternak let's review this in light of that.

[SzymonPobiega]

Here's the article that describes AlwaysOn vs cross-catalog transactions: https://technet.microsoft.com/en-us/library/ms366279(v=sql.130).aspx. My understanding is not supported but the wording is a bit confusing. Should we try it and verify?

[tmasternak]

I think that we should try a spike and verify our assumptions.

[MarcinHoppe]

Spike issue has been created: #325.

[SzymonPobiega]

Fixed by #330