feature(provisioner) Add a default mssql provisioner

[Hentouane]

Adding a new default provider for a mssql database.

Description

Created a new default provider template for a mssql db based on already existing mysql and postgres ones. Updated zz-default.provisioners.yaml and README.md.

What does this PR do?

Adding a new default provider for a mssql database per feature request #66

Was tested with the following score.yaml file:

apiVersion: score.dev/v1b1
metadata:
    name: test-container
containers:
    main:
        image: mcr.microsoft.com/mssql-tools
        variables:
            SERVER_NAME: ${resources.db.host}
            MSSQL_SA_USER: ${resources.db.username}
            MSSQL_SA_PASSWORD: ${resources.db.password}
        command:
            - /bin/sh
            - -c
            - /opt/mssql-tools/bin/sqlcmd -S $SERVER_NAME -U $MSSQL_SA_USER -P $MSSQL_SA_PASSWORD -Q "select @@version"
resources:
    db:
        type: mssql

Once deployed in a k3s cluster, the following was succesfully logged by the test-container:

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 
Microsoft SQL Server 2022 (RTM-CU15-GDR) (KB5046059) - 16.0.4150.1 (X64)                                                                                                                                      
     Sep 25 2024 17:34:41                                                                                                                                                                                      
     Copyright (C) 2022 Microsoft Corporation                                                                                                                                                                  
     Developer Edition (64-bit) on Linux (Ubuntu 22.04.5 LTS) <X64>                                                                                                                                            
                                                                                                                                                                                                               
  (1 rows affected)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• New chore (expected functionality to be implemented)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've signed off with an email address that matches the commit author.

[mathieu-benoit]

Thanks @Hentouane for your contribution.

I have left a few comments for updates.

Also, you need to sign your commits to be compliant with the DCO check, see here how to resolve it: https://github.com/score-spec/score-k8s/runs/31986670494.

[Hentouane]

Commits were signed-off and changes were applied. Leaving one conversation open as to confirm reviewer's approval.

[mathieu-benoit]

Thanks, @Hentouane!

LGTM

@astromechza, another pair of eyes for this review please? Thanks1

[astromechza]

Yup, this looks good to me! Definitely a good starting point for those using mssql

Thanks @Hentouane 👍