Update custom project workflow files

[Ekhorn]

Description

Brings the custom project workflows up to date and adds manual deployments. The following has been tested: #2955 (comment)

• Ref Migrate custom projects over to the new custom project environment workflows #2955

Decisions

• Separate custom-install-dist.yml: the archive steps in install-dist.yml assume the core repo layout (e.g. ui/util) and fail in custom projects. Nothing in the custom pipelines downloads those artifacts, so the custom build only runs installDist. It includes the deployment, so a broken deployment build shows up in review.
• Staging only deploys when configured: the deployment job runs only when .ci_cd/ci_cd.json has a deploy entry for the pushed branch, as in the old ci_cd.yml. Without this check, deployment.yml fails on projects without deploy config.
• Support for older deploy.sh versions: custom projects run deploy.sh from their openremote version. Up to 1.32.0 that script reads IS_MAIN_REPO and openremote/.ci_cd, so deployment.yml now provides both, like ci_cd.yml does. Without them host init is silently skipped.
• custom-deploy.yml wrapper: custom projects call this instead of deploy.yml or deployment.yml, so they don't depend on the deployment.yml workflow (inputs), which we plan to change in Investigate how to simplify the deployment workflows #2801.
• Code coverage left for later: code-coverage.yml needs JaCoCo outputs and the combinedCoverageReport task. Adopting it means running it only for custom projects that support it.

Warning

The GFE_PASSWORD mechanism for decrypting encrypted deployment files has not been tested. (This has now been tested)

Changelog

• Add custom-install-dist.yml that builds custom projects without archiving core build outputs
• Use custom-install-dist.yml in custom-review.yml and custom-staging.yml
• Enable the deployment job in custom-staging.yml when .ci_cd/ci_cd.json configures a deploy for the branch
• Support deploy.sh from releases up to 1.32.0 in deployment.yml
• Add custom-deploy.yml for manual deployments from custom projects

Checklist

• 1. Acceptance criteria of the linked issue(s) are met
• 2. Tests are written and all tests pass
• 3. Changes are manually tested by you and the reviewer
• 4. Documentation is written or updated

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wborn]

This is an initial AI-assisted review.

The custom-project workflow improvements look good overall. One deployment safety issue should be addressed before merging: automatic deployments need to wait for lint validation.

There is also a non-blocking suggestion regarding build validation for deployment-only changes.

[wborn]

The deployment job doesn't depend on check-spotless or ui-check-spotless, so it can start before those checks finish and proceed even if lint fails. Could both lint jobs be added to needs to ensure validation completes successfully before deploying?

[wborn]

The new custom-install-dist.yml includes the deployment build, but any_modified still excludes deployment/**. Consequently, deployment-only changes won't trigger the build. Could the change detection be extended to cover those files as well?