Changing port numbers at runtime leads to deployment errors when using K8s/OpenShift extensions

[Sgitario]

Describe the bug

Something else I saw today is that the port configuration (for Management and HTTP configuration) are runtime properties.

This means that if users change the port number at runtime, the generated manifests for OpenShift / Kubernetes will stop working.

I would say this is a very major issue, though the fix (changing these properties to be build-time-only properties) implies adding a strong limitation for users (since users won't be able to update the port to use any longer).

Not sure if we can / or make sense to allow changing these properties if and only if the Kubernetes extension is not present.

Relates #32225 (comment)

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand (kubernetes,openshift), @iocanel (kubernetes,openshift)