feat: add hostPorts support to component network configuration

[dudizimber]

fix #9818

[apecloud-bot]

Auto Cherry-pick Instructions

Usage:
  - /nopick: Not auto cherry-pick when PR merged.
  - /pick: release-x.x [release-x.x]: Auto cherry-pick to the specified branch when PR merged.

Example:
  - /nopick
  - /pick release-1.0

[CLAassistant]

All committers have signed the CLA.

[dudizimber]

@shanshanying @leon-inf

It took me some fiddling to get the project running, but I was able to confirm that this change does behave properly.
To set the HostPort, the Cluster manifest should be changed like so:

...
  annotations:
    kubeblocks.io/host-network: "falkordb"
... 
  componentSpecs:
  - name: falkordb
     network:
       hostPorts:
       - name: falkordb
          port: 6379
...

[leon-inf]

falkordb

👍🏻

You can set the network.hostNetwork to true instead of adding the annotation.

[dudizimber]

falkordb

👍🏻

You can set the network.hostNetwork to true instead of adding the annotation.

Thanks. Let me know if anything else is required before merging.

[leon-inf]

The API should clarify whether all host-network ports need to be specified. Also, if not, what is the default behavior of other ports.

[leon-inf]

In addition, how should the ports built into the KB be specified? For example, the HTTP port of kbagent.

[leon-inf]

HostPort or HostPortPort?

[leon-inf]

The resolving to host-network ports in Vars also needs to be modified.

[dudizimber]

@leon-inf I'm gonna need some help on this one...
From what I understand, I must add the predefined port name to the synthesized component no? In the kbappsv1.HostNetwork type.

[dudizimber]

Fixed in #9892