ci: publish development images via repository variables

[ToxicBiohazard]

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply.

• Bugfix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality not to work as expected).
• Documentation Update (if none of the other choices applies).

Proposed changes

Development and production images are both published by the shared build workflow. A push to main, a manual run, or a release-candidate tag publishes a development image. Any other version tag publishes a production image. The previous production rollout is removed.

Checklist

Put an x in the boxes that apply.

• I have read and followed the CONTRIBUTING.md
  doc.
• Lint and unit tests pass locally with my changes.
• I have added the necessary documentation (if appropriate).

Additional context

Workflow-only change. No application code was modified.

The development and production environments need these variables before an image can be published:

• AWS_GITHUB_ROLE
• ECR_REPOSITORY

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.60%. Comparing base (76b2f25) to head (da5635a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #193   +/-   ##
=======================================
  Coverage   66.60%   66.60%           
=======================================
  Files          54       54           
  Lines        3177     3177           
=======================================
  Hits         2116     2116           
  Misses       1061     1061           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dimoschi]

LGTM, thanks for taking care!