Move the deploy feature out into its own release archives

[bep]

I have received a question/report about some questionable network activity from Hugo on Windows. This is from a more complex setup that is not practical for me to set up, but I have inspected the code and my prime suspect is the hugo deploy command (the Microsoft Azure integration), which does static initialisation, even if you don't use the feature. We really need to make this feature some kind of plugin (e.g. Wasm), but until then I suggest we pull it out into separate release archives.

We already have a nodeploy build tag for this, so that should not be too hard.

[jmooring]

Does that mean we need to do something like this?

Edition name	File name
standard	hugo_0.136.5_linux-amd64.tar.gz
extended	hugo_extended_0.136.5_linux-amd64.tar.gz
standard/deploy	hugo_with_deploy_0.136.5_linux-amd64.tar.gz
extended/deploy	hugo_extended_with_deploy_0.136.5_linux-amd64.tar.gz

[bep]

Does that mean we need to do something like this?

I thought about making it a little bit simpler and only create deploy variants for the extended images, so something ala:

Edition name	File name
standard	hugo_0.136.5_linux-amd64.tar.gz
extended	hugo_extended_0.136.5_linux-amd64.tar.gz
extended/deploy	hugo_extended_with_deploy_0.136.5_linux-amd64.tar.gz

[jmooring]

That looks good to me.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.