Add link to sample CI for an app with SQLProvider

[jzsampaio]

The linked project includes CI and a Dockerfile for a sample app that uses SQLProvider.

Proposed Changes

The lack of guidelines on how to build and deploy a project w/ SQLProvider has delayed my team from taking SQLProvider to production. We have documented our solution on a sample repo, and we think the community could benefit from it.

Types of changes

What types of changes does your code introduce to SQLProvider?
Put an x in the boxes that apply

• Bugfix (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 not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Build and tests pass locally
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

[Thorium]

Thanks for the PR and sorry for not merging it, but the statement that "you will need a working database connection" is simply not true. There are multiple options to do CI:

• You can use ContextSchemaPath to serialize the database schema to JSON: https://fsprojects.github.io/SQLProvider/core/parameters.html#ContextSchemaPath
• When using SQL Server, you can use the SSDT provider which doesn't need connection: https://fsprojects.github.io/SQLProvider/core/mssqlssdt.html#Advantages-of-using-the-SSDT-provider
• That being said, I appreciate much your tutorial project to use containers to solve CI, that's also nice option.