Fidesops 78 mssql support

[eastandwestwind]

Purpose

Adds SQL Server support

Changes

• Adds connection support for mssql
• Adds connection integration tests for mssql
• To manually test, in Postman PUT {{host}}/connection/{{mssql_key}}/secret, use the following url: "mssql+pyodbc://sa:Mssql_pw1@mssql_example:1433/mssql_example?driver=ODBC+Driver+17+for+SQL+Server", alternatively you can break each part out into separate components, refer to connection_secrets_mssql.py.

Checklist

• Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram
• Good unit test/integration test coverage

Ticket

Fixes #78

[pattisdr]

great work @eastandwestwind - the main additional piece I'd like to see is to try to get the mssql_example database created and populated when we run make integration-env, not just creating it in the integration tests

[eastandwestwind]

Ok, @pattisdr , over to you again! I cleaned up the PR based on your suggestions, and was able to get logs to print for make integration-env using your suggestion: @docker-compose -f docker-compose.yml -f docker-compose.integration-test.yml logs -f -t.

I also reused the @docker exec -it fidesops python tests/integration_tests/mssql_setup.py step for spinning up the test db for integration tests.

[pattisdr]

great will take a look!

[pattisdr]

Nice @eastandwestwind 🏆 - i really liked your solution to bring up the docker containers in detached mode, then exec into the fidesops container to run the python mssql initialization script to get around the M1 + MSSQL issues when we're trying to create a test mssql_example database on make integration-env.

just one quick point and I think this is good to go

[pattisdr]

I think we might want to only call this if we're running this file directly (which will set the __name__variable as __main__) and not call this when we import it:

if __name__ == "__main__":
    mssql_setup()

[eastandwestwind]

ohh I see, good catch!