refactor: Restructure values in service profiles.

[pantierra]

This introduces Service Profile presets for common deployment scenarios:

• profiles/core.yaml - Production-ready deployment with stable services only (STAC, Raster, Vector)
• profiles/experimental.yaml - Full feature set including experimental components (Multidim, STAC Browser, Notifications, Knative, Monitoring)
• profiles/local/k3s.yaml - k3s-specific overrides for local development (inherits from experimental)
• profiles/local/minikube.yaml - Minikube-specific overrides for local development (inherits from experimental)
• And some profiles documentation in profiles/README.md

What i have done? Reorganized local development values files into structured profiles directory:

• Moved local-base-values.yaml to profiles/experimental.yaml
• Moved local-k3s-values.yaml to profiles/local/k3s.yaml (now inherits from experimental)
• Moved local-minikube-values.yaml to profiles/local/minikube.yaml (now inherits from experimental)
• Updated deploy.sh script to use new profile paths

[ciaransweet]

I'd maybe consider these 'production/core'?

[pantierra]

I would prefer to keep the core.yaml rather conservatively small. But it probably makes sense to add a production.yaml version with them being enabled. Kind of a "what we would deploy for a partner usually". But maybe in another PR?

core.yaml should be more like the things we are confident they are stable. Potentially also give a different warning on these when there are breaking changes than on the others.

[ciaransweet]

I would maybe change the wording around it then as it mentions Production-ready deployment

Which yes, but I would say maybe stable

Fits the counterpart that is experimental

[pantierra]

Thanks a lot for the review!