Have zero-downtime deployments

Due to the nature of the deployment of an Azure Function and running it from a package there is downtime at the moment.

Deployment of the Bicep file causes the run from package configuration setting to be set to `1`, and not the URL where the package is located. This value is updated to the URL when the actual zip-file is uploaded.

Change this to a two-step deployment, similar to what has been done in the Minifier solution where this is also done in two deployment steps (https://github.com/Jandev/minifier/blob/develop/.github/workflows/release.yml).
First upload the zip file, get the correct URL and then use the URL as an input parameter to the Bicep files and set the correct configuration value.

Start by comparing the current deployment workflow and Bicep files with the two-step pattern in the referenced Minifier release.yml. Trace how the zip URL is produced and passed into the Bicep deployment; done means the package is uploaded before configuration is applied and the Azure Function retains its package URL without deployment downtime.

Written by the indexing model from the issue text.