fixing context image not created when manually running releases

[nammn]

Summary

This pull request includes several updates to improve code readability, streamline imports, and enhance observability in the mongodb-kubernetes project. The changes encompass YAML file formatting, Python test import simplifications, and additional tracing attributes in the pipeline logic.

Pipeline Enhancements:

• Updated the should_skip_arm64 function in pipeline.py to accept a BuildConfiguration parameter. Otherwise - we are skipping arm64 releases during manually triggered releases
• Added OpenTelemetry tracing attributes to capture architecture details and release metadata in the get_architectures_set, inner, and build_image_generic functions, improving observability. [1] [2] [3].
  • the idea here is to add as much visibility as I could easily add

Proof of Work

• passing ci

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[nammn]

that should go away with this: #210

[mircea-cosbuc]

LGTM. I added some suggestions to avoid confusion later when revisiting the code.