feat: deploy local-path-provisioner as an rke2 addon

[madalazar]

Description

Purpose of this PR is to set-up and deploy Rancher Local Path Provisioner as an add-on using RKE2 as a provider. This work is required in i-67996.

Details about the changes

• My first thought was to store and process the LPP manifest locally mainly to stop any changes being done to it in the future. Instead we not have a lot of Trivy issues. We might need to just pull it in via curl/wget but will wait to see people's opinions on this matter.

• I'm setting up LPP with similar parameters as I've seen done in K3s (including deploying in the kube-system ns)

• I was not able to get LPP as an add-on to work with the base extensions with OpenEBS ( I think this is a configuration issue - I tried marking the local-path storageclass as not default and I've moved LPP out into its own namespace but no luck).
  If we want to deploy this CM change separately to base-extension, then the scenario above ^^ requires more debugging to understand. I would start by checking how does the add-on set-up of LPP differ to the base extension deployment used in https://jira.devtools.intel.com/browse/ITEP-27893.

If we are comfortable deploying the changes from CM and ClusterExtensions (open-edge-platform/cluster-extensions#71) at the same time I think the scenario above can be ignored.

Any Newly Introduced Dependencies

No new dependencies were added

How Has This Been Tested?

CO - RKE2 with LPP, base extensions w OpenEBS

• [Y] cluster successfully deployed

• [N] apps successfully deployed, observability is up, metrics are showing
  I tried marking the local-path storageclass as not default, move the LPP set-up into its own namespace.

CO - RKE2 with LPP, base extensions without openebs

• [Y]cluster successfully deployed

• apps successfully deployed

• observability is up, metrics are showing

Checklist:

• I agree to use the APACHE-2.0 license for my code changes
• I have not introduced any 3rd party dependency changes
• I have performed a self-review of my code

[github-advanced-security]

Trivy found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[gcgirish]

PR open-edge-platform/cluster-connect-gateway#64 needs to merge first.

[gcgirish]

Lgtm. Couple of questions.

1. From my understanding of default-cluster-templates/manifests/embed_lpp_manifest.sh, it does not embed the lpp manifest to template if it already exists. Correct? Just checking, because that is what we need
2. No change for k3s because lpp is part of k3s binary - correct?