Currently the wikibase release pipeline only runs for a single environment variable file at a time.

Historically, when the pipeline was first created, this env file was meant to point to the latest and greatest versions of each component.
As new commits were made to components ,(such as wikibase), the pipeline would run and CI would indicate a red or green build.

In the present day the single env var points to the latest release that was made from the pipeline (currently wmde.10)
For the past 2 years or so running against the latest and greatest versions of components would have been red, and there were not the resources available to fix the issue that cropped up.

I would propose that we slightly modify the GitHub Actions workflows for the pipeline to enable running for multiple .env files at once.

This initially will support the current pattern of supporting 2 releases of wikibase at once.
(Rather than needing to do releases such as security releases one PR at a time).
And in the future it would easily enable the running of a "latest" version of the components once again.