kubernetesRuntime read metricsPort from kuberbetesRuntimeFactoryConfig

[zzzming]

Fixes

The bug is Kubernetes function runtime's prometheus metrics port always binds to a random available port instead of using the metricsPort specified in FunctionRuntimeFactoryConfig from the functions_worker.yaml or default to 9094 from the KubernetesRuntimeFactoryConfig class.

This is a fix to address a bug introduced by this PR (#9610)

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

• no-need-doc

[github-actions]

@zzzming:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

[github-actions]

@zzzming:Thanks for providing doc info!

[eolivelli]

can you please add some unit tests ?

[lhotari]

I created #14502 with tests and handling for disabling Prometheus Metrics for Pulsar Functions.