Refactor logic for determining deployment environments and deployment script

[mazhelez]

❔What, Why & How

What: Refactor logic for determining deployment environments and deployment script

Why: Currently, environment settings deployTo<envName> isn't taken into account during deployment.

How: Applying the following logic:

• DetermineDeploymentsEnvironments action should not calculate deployment settings: they should be calculated in the Deploy action per environment.
• DetermineDeploymentsEnvironments should only calculate shell, runs-on and enviromentName, as they are needed runtime to construct the deployment matrix.
• Settings that are read during the deployment jobs should be taken into account when calculating the deployment configuration.

Related to issue: no active issue at the moment

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry
• Test on a sample repository: https://github.com/BusinessCentralApps/bcsamples-bingmaps.ptetest/actions/runs/18221324273/job/51887733482 (Environment authentication fails, but logs show that deployTo settings are applied from env variable)
• E2E test run: https://github.com/microsoft/AL-Go/actions/runs/18196126893