MSSQL allow to define different databases for login an user

[bakito]

Description of your changes

When a MSSQL user is created in a database other than the master database. The USER needs to created in the dedicated database, but the LOGIN needs to be created in the master database.

This is also mentioned here: #158 (comment)

This pull request adds the possibility to define an additional database, where the login object is created in.
The already existing database fields are used for the user statements.

If the newly introduced loginDatabase is not set, the database field is used for both operations as before.

Fixes #158

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.

How has this code been tested

The application was built and deployed in an existing cluster. Where the User rewource was configured to use the loginDatabase: master and databaseRef that is pointing to a Database resource.

apiVersion: mssql.sql.crossplane.io/v1alpha1
kind: User
metadata:
  name: sql-example-user
spec:
  forProvider:
    loginDatabase: master
    databaseRef:
      name: test-db
    passwordSecretRef:
      key: password
      name: sql-example-user-pw
      namespace: crossplane-system
  writeConnectionSecretToRef:
    name: sql-example-user-connection-secret
    namespace: crossplane-system

[bakito]

@turkenh sorry to bother you, but who can review this PR?

[bakito]

@Duologic thank you for approving the pipeline. I updated the branch to hopefully also get the publish-artifacts action become green.

Could you please re-approve the pipelines to run?

thx