fix helm manifests to support 2.16 jaeger configs

[DaedalusG]

closes PLAT-485

Update manifests to support 2.16 jaeger configurations style

This follows changes to the sourcegraph jaeger base image https://github.com/sourcegraph/sourcegraph/pull/10912

Test plan

See testing from original PR, this version of the charts was tested via kind

Tested by generating a template of the jaeger deployment and running

helm unittest charts/sourcegraph -f 'tests/otelCollectorJaeger_test.yaml' -f 'tests/otelAgentHostPort_test.yaml' 2>&1

[michaellzc]

can we update the CHANGELOG to indicate this is a breaking change?

also might want to do a changelog post in sg/sg as well

[michaellzc]

also CI is complaining about outdated dodcs

[DaedalusG]

can we update the CHANGELOG to indicate this is a breaking change?

also might want to do a changelog post in sg/sg as well

@michaellzc did you mean the changelog in this repo, or the changelog product on main? The changelog in here isn't really that robust in its release tracking

[michaellzc]

can we update the CHANGELOG to indicate this is a breaking change?
also might want to do a changelog post in sg/sg as well

@michaellzc did you mean the changelog in this repo, or the changelog product on main? The changelog in here isn't really that robust in its release tracking

I was thinking both, but you're right. let's just do sg/sg.

[Chickensoupwithrice]

other than marking as breaking change, this seems good

[sourcegraph-release-bot]

The backport to 7.1.x failed at https://github.com/sourcegraph/deploy-sourcegraph-helm/actions/runs/23320836778:

Reviews may only be requested from collaborators. One or more of the teams you specified is not a collaborator of the sourcegraph/deploy-sourcegraph-helm repository.

To backport this PR manually, you can either:

Via the sg tool

Use the sg backport command to backport your commit to the release branch.

sg backport -r 7.1.x -p 841

Via your terminal

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.1.x 7.1.x
# Navigate to the new working tree
cd .worktrees/backport-7.1.x
# Create a new branch
git switch --create backport-841-to-7.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1b6f92b83fe858207be75b261b1c80754482227e
# Push it to GitHub
git push --set-upstream origin backport-841-to-7.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.1.x

If you encouter conflict, first resolve the conflict and stage all files, then run the commands below:

git cherry-pick --continue
# Push it to GitHub
git push --set-upstream origin backport-841-to-7.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.1.x

• Follow above instructions to backport the commit.
• Create a pull request where the base branch is 7.1.x and the compare/head branch is backport-841-to-7.1.x., click here to create the pull request.

Once the pull request has been created, please ensure the following:

• Make sure to tag @sourcegraph/release in the pull request description.

• kindly remove the release-blocker from this pull request.