Add basePath option for Jaeger

[lambertjosh]

What this PR does / why we need it:

Jaeger has added a new option to set the base path of the query UI, which makes it usable behind reverse proxies. This option should also be exposed in the chart as well.

PR which added this support: jaegertracing/jaeger#748
Docs on set up: https://www.jaegertracing.io/docs/deployment/#ui-base-path

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #7489

Special notes for your reviewer:

[lambertjosh]

/assign @viglesiasce

[cpanato]

/lgtm

[cpanato]

/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cpanato, lambertjosh
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: viglesiasce

If they are not already assigned, you can assign the PR to them by writing /assign @viglesiasce in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@lambertjosh: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-charts-e2e	a1bbdde	link	/test pull-charts-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[lambertjosh]

@cpanato thanks for reviewing, the errors in the deploy are unrelated to this PR as they also occur in the current published version. (Probably a change in the cassandra dependency.)

What is the best way to proceed here? Are we blocked from changes until someone fixes whatever issue is going on with cassandra?

[cpanato]

@lambertjosh I will try to check later this week what is happening 😄

[lambertjosh]

Actually it looks like there is an existing issue here working on the cassandra problem: #7407

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity.