Automatically re-create initial migrations when building a release of FSH

[fretje]

Re-creating the initial migrations could probably be further automated and should be part of the build process (CI pipeline) of the fsh project when creating a new release...

The https://github.com/fullstackhero/dotnet-webapi-boilerplate/blob/main/scripts/add-update-db-migrations.ps1 script gets us there partly. But it needs all the different databases installed to be able to use it.
I think it would be possible to create a script that starts docker containers with the individual databases and uses those to generate the initial migration scripts, so it can be run anywhere regardless of which database engines are installed locally. It could then even be part of the CI pipeline (github actions) that actually builds the release.

[FaroukOyekunle]

@fretje & @iammukeshm has this Issue been resolved?