feat[common]: merge portal with chartContext and refactor

[PrivatePuffin]

Is your feature request related to a problem?

We currently have both portal and chartContext which contain "derived" values, such as ways to reach the chart.
This gets used by the notes.txt to showcase how to reach a chart, for example.

However, this is too bloated.
portals should be part of chart-context and should be dynamic.

The portal info is also the thing that should be used when ranging over the hostnames a chart is available at, not ingress.
As we would soon be supporting both gateway-api AND ingress

Describe the solution you'd like

portals should be part of chart-context and should be dynamic.

• Fetch all Loadbalancer-type services and their ports
• Fetch all ingresses and the service+port they are linked to

Create an entry in portals:

• If ingress has a service-port assigned, show the ingress hostname(s)
• Else show loadbalancerIP+port

Describe alternatives you've considered

.

Additional context

If something has ingress, just assume https and port 443 (aka no port).

Currently we do all sorts of complicated fetching to figure out end-point URLs.
But if users want to go as far as having ingress (or gateway-API) on non-standardized ports, instead of just relying on host-name filtering, we shouldn't bother.

It creates a mess and would inherently create reliances on lookups we dont want.

This also means a support policy update:
"We do not support running ingress or gateway-api on any port other than 80/443 and only using https"

I've read and agree with the following

• I've checked all open and closed issues and my request is not there.
• I've checked all open and closed pull requests and my request is not there.