fix(manager): declare status port in tikv pods

[omar-mohamed-khallaf]

What problem does this PR solve?

When scraping pods with victoriametrics, it automatically drops targets (pods in this case) that don't have the port to scrape declared in its spec.ports.

What is changed and how does it work?

Declared the status port in the pod spec.

Code changes

• Has Go code change
• Has CI related scripts change

Tests

• Unit test
• E2E test
• Manual test
• No code

Side effects

• Breaking backward compatibility
• Other side effects

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release Notes

NONE

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign charleszheng44 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

[sre-bot]

All committers have signed the CLA.

[ti-chi-bot]

Welcome @omar-mohamed-khallaf! It looks like this is your first PR to pingcap/tidb-operator 🎉

[csuzhangxc]

if we update the Pod spec directly, all TiKV pods will be re-created after the TiDB Operator is upgraded, this may be not acceptable for some users.

[omar-mohamed-khallaf]

They will be recreated one by one, right?
What should I do?