Bug: The SQLSRV driver ignores the port value from the config.

[iRedds]

Description
Fixes #6032

The SQLSRV driver ignores the port value from the config.

This PR fixes a bug.
Also, if a port is already specified in the hostname, the port from the configuration will be ignored.

It seems to me that the default tests are enough, because the database connection settings for the tests use the default port, which was ignored when configuring the connection.

Checklist:

• Securely signed commits

[kenjis]

Ref https://www.php.net/sqlsrv_connect

[kenjis]

It seems to me that the default tests are enough, because the database connection settings for the tests use the default port, which was ignored when configuring the connection.

This bug was not detected by the existing tests, so tests are not enough.
But to test this, we build another SQL Server with the different port.
It costs a lot.

I've confirmed Port 1444 server can be connected with this PR.

[iRedds]

@kenjis I don't see the point in an additional server.
We can use non-standard ports for each DBMS for github actions and in test configs. Or at least change the ports in the docker containers to listen.

[kenjis]

@iRedds Okay, you are correct.
Changing the port of the docker containers to listen is enough.