Dockerize commands for the dotnet namespace

[Davane]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This pull request aims to containerize the dotnet commands so that docker is the only dependency that you will need when working with Frontier created dotnet project. The following features were also added:

• Ability to include sentry or not using flags when creating the project.
• Hot reloading when changes are made within the project.
• Ability to specify the environment when running migration commands using flags.
• Ability to specify the configuration when running migration commands using flags (Debug or release).
• (Experimental) Added the ability to remove applied migrations from the DB.
• (Experimental) Ability to specify the Dotnet SDK version (Docker Image) to use and create the project.

Caveat

• A side effect of the hot reload feature is that when migrations are created the hot reload functionality will pick this up as a change within the project and automatically apply the migration to the DB.
• Starting up the project for the first time will cause errors related to the unapplied migrations but once you create the initial migration and start the project again then the errors will be gone. This might be related to the the fact that the project is trying to applied existing migrations during startup but because no DB exists it is failing.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly

[Davane]

@marlonajgayle & @andre-vidal Can you review when you get a chance?

There are also changes in the dotnet template as well marlonajgayle/dotnet-web-api-template#33