Provide Oracle like database.url to support named instances [DBZ-5593]

Migrated from [DBZ-5593](https://issues.redhat.com/browse/DBZ-5593)

h1. Feature request or enhancement

This is a feature request
h2. Which use case/requirement will be addressed by the proposed feature?

When using the sqlserver connector, the "database.port" property is a required field with the default value of 1433.  This is problematic when you have a named instance and the port is not configured with the default port.  There needs to be a way via the properties to indicate that the "database.port" property is not provided and to not default to the default port (1433).
h2. Implementation approach

I have already implemented a solution for this and would like to commit for review.  The approach includes the definition of a new property ("database.noport") and the definition of a new URL Pattern that doesn't include the port in the jdbc connection string.  When creating the ConnectionFactory, if the "noport" property exists then a ConnectionFactory is created using the url pattern without the port in the string.  Otherwise, a ConnectionFactory is created using the existing url pattern.

Start by locating the SQL Server connector's database properties, JDBC URL patterns, and ConnectionFactory creation described in the issue. Verify how the new no-port property should bypass the default 1433 port and confirm completion with connector tests covering named-instance connections.

Written by the indexing model from the issue text.