Pre-build mmWave Firmwares

[gnumpi]

GH-Workflows:

• use local copy of workflow for building firmware (supports building variants having the same device name)
• run deployment script on docu repo only when calling build_and_release workflow from main and staging
• naming of release assets is taking from the input config file: e.g. satellite1.VARIANT.yaml -> satellite1.VARIANT.factory.bin

Config files:

• renamed satellite1.yaml -> satellite1.dashboard.yaml
• renamed satellite1.factory.yaml -> satellite1.yaml
• introduces satellite1.ld2410.yaml
• introduces satellite1.ld2450.yaml

Requires:
FutureProofHomes/Documentation#111. merged

! Don't use release actions in this branch before the documentation deployment script has been updated !

[gnumpi]

TODO:

• cleanup branch before merging
• check with @that1guy if renaming the config files require any documentation updates
  ( I didn't find any impact on the documentation)
• merge version updates from main_plus_mmWave_prebuild
• check if dashboard building works as expected
• check if each firmware variant updates from the correct update channel
  (seems to work in general, but initial update check can delay up to 3h)