fix: avoid stderr/stdout mixing in single_e2e.sh chart_info parsing

[MaciejKaras]

Summary

scripts/evergreen/e2e/single_e2e.sh used 2>&1 when capturing chart_info from oci_chart_info.py. This caused Python's urllib3 RequestsDependencyWarning (emitted on stderr) to be prepended to the JSON stdout, producing a mixed string like:

.../requests/__init__.py:113: RequestsDependencyWarning: urllib3 ...
  warnings.warn(
{"repository": "dev/mongodb/helm-charts", "registry": "...", ...}

When this string was then piped into jq, it failed with: jq: parse error: Invalid numeric literal at line 1, column 102

Before:

if ! chart_info=$(scripts/dev/run_python.sh scripts/release/oci_chart_info.py \
    --build-scenario "${BUILD_SCENARIO}" 2>&1); then
    echo "${chart_info}"
    exit 1
fi
helm_oci_registry=$(echo "${chart_info}" | jq -r '.registry' )
...

After:

chart_info=$(scripts/dev/run_python.sh scripts/release/oci_chart_info.py \
    --build-scenario "${BUILD_SCENARIO}") || { echo "Failed to generate chart_info" ; exit 1; }

helm_oci_registry=$(echo "${chart_info}" | jq -r '.registry') || { echo "Failed to parse registry from chart_info"; exit 1; }
...

Removing 2>&1 means:

• chart_info only ever contains clean JSON stdout
• Errors (stderr) are printed naturally by the failing command before || triggers
• Each jq extraction has explicit error handling that was missing before

Proof of Work

Tested with --build-scenario patch:

• Python warnings print to terminal (stderr) as expected
• chart_info contains clean JSON
• All four fields (registry, repository, region, version_prefix) parse correctly

Error path verified: passing an invalid scenario prints the error from stderr, then the context echo fires — no mixed content in variables.

  echo "=== Test 1: chart_info command failure (invalid scenario) ===" && \
  chart_info=$(scripts/dev/run_python.sh scripts/release/oci_chart_info.py --build-scenario invalid_scenario 2>/dev/null) || \
  { echo "Failed to generate chart_info"; } && \
  echo "" && \
  echo "=== Test 1 (with stderr visible, as it would be in the script) ===" && \
  chart_info=$(scripts/dev/run_python.sh scripts/release/oci_chart_info.py --build-scenario invalid_scenario) || \
  { echo "Failed to generate chart_info"; }

  === Test 1: chart_info command failure (invalid scenario) ===
  Failed to generate chart_info
  === Test 1 (with stderr visible, as it would be in the script) ===
  /Users/maciej.karas/mongodb/mongodb-kubernetes/venv/lib/python3.13/site-packages/requests/__init__.py:113 RequestsDependencyWarning: urllib3 (2.6.3) or chardet (7.0.1)/charset_normalizer (3.4.4) doesn't match a supported version!
  warnings.warn(
  usage: oci_chart_info.py [-h] -b
  oci_chart_info.py: error: argument -b/--build-scenario: invalid choice: 'invalid_scenario' (choose from release, patch, staging, development)
  Failed to generate chart_info
  <exited with exit code 0>

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 added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.7.1 Release Notes

Other Changes

• Container images: Merged the init-database and init-appdb init container images into a single init-database image. The init-appdb image will no longer be published and does not affect existing deployments.
• Helm Chart: Removed operator.baseName Helm value. This value was never intended to be consumed by operator users and was never documented. The value controls the prefix for workload RBAC resource names (mongodb-kubernetes default), but changing it could break the operator and workloads because the operator is not aware of custom prefixes. With this change, the Helm chart will no longer allow customisation and the relevant resources will be deployed with predefined names (ServiceAccount with names mongodb-kubernetes-appdb, mongodb-kubernetes-database-pods, mongodb-kubernetes-ops-manager, Role with name mongodb-kubernetes-appdb and RoleBinding with name mongodb-kubernetes-appdb).