Fix harbor/grafana on upgrade

What does this MR do and why?

Lately we noticed multiple failures on nightly upgrade pipeline due of harbor/grafana login in tests. See some examples:

https://gitlab.com/sylva-projects/sylva-core/-/pipelines/1469490282

https://gitlab.com/sylva-projects/sylva-core/-/pipelines/1469490459

I was trying to replicate this behavior in my test environment and I've seen after upgrade the ingress for harbor/grafana does not set the proper address and is not able to resolve it.

The aim of this MR is to fix that issue by setting the ingressClassName.

Related reference(s)

Closes #1643 (closed)

Test coverage

CI configuration

CI pipelines perform an update for both management and workload clusters, this update will NOT perform a ClusterAPI rolling update (deletion and creation of new K8s nodes) by default.

For some cases, it may be relevant to perform more complex tests.

Theses features can be activated in an MR by adding one of these labels to the MR and will apply to the next pipelines.

• adding the label ci-featuretest-rolling-update pipelines will perform a node rolling update in the -update jobs (without version upgrades)
• adding the label ci-featuretest-upgrade-from-1.1.1 pipelines will perform an upgrade from Sylva 1.1.1 to your dev branch (including a k8s version upgrade resulting in a node rolling update)