[release/v7.5] Fix variable reference for release environment in pipeline

[pwshBot]

Backport of #26012 to release/v7.5

Triggered by @TravisEz13 on behalf of @TravisEz13

Original CL Label: CL-BuildPackaging

/cc @PowerShell/powershell-maintainers

Impact

Choose either tooling or Customer impact.

Tooling Impact

• Required tooling change
• Optional tooling change (include reasoning)

Customer Impact

• Customer reported
• Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Regression

• Yes
• No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

• High
• Medium
• Low

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

[TravisEz13]

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[microsoft-github-policy-service]

📣 Hey @@pwshBot, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms

[pohi99999]

This pull request makes a minor update to the .pipelines/PowerShell-Release-Official.yml file, correcting the way the ob_release_environment variable is set in the pipeline configuration.

• Changed the assignment of ob_release_environment from using the parameters.releaseEnvironment to variables.releaseEnvironment for consistency and correctness in variable usage.