feat: move default node collector port to avoid conflicts and add setting in config

[blumamir]

Since node collector runs as a DaemonSet with host network (so that otlp ports 4317 and 4318 are accessible from the pods exporters), it also shares the ports namespace with the node.

The ports it binds to might conflict with ports of other tools installed in the cluster that does similar things, and in this case data collection will fail to start with error: "listen tcp 0.0.0.0:8888: bind: address already in use".

The collectors currently expose and scrape their own metrics on port 8888 which is good candidate for collistions.

This PR:

• makes the default port for own telemetry endpoint for node collector 55682 to have low chance of collision with something that already runs on the node (instead of using 8888 as default).
• Adds an option to odigos config to set the port, in case one needs it hard-coded to a specific value to manage the public ports on the node).

The port to use is written on the collectors group CRD by the scheduler to abstract away the default and odigos config resolving, and allow the resolved value to be more easer to consume.

For the cluster collector, the collector runs as deployment with k8s service, thus we can safely use 8888 without colliding with anything else

[RonFed]

Wrote a few small non blocking comments