📝(docs) fix k8s local cluster installation guide

[alexandresib]

Summary

• Fix all helm chart --repo URLs pointing to GitHub Pages (suitenumerique.github.io) with direct GitHub repo URLs (github.com/suitenumerique) for helm-dev-backend and the drive chart
• Add a "Populate the CA certificate bundle" section explaining how to load the mkcert root CA into a Kubernetes ConfigMap before deploying
• Update drive.values.yaml: add REQUESTS_CA_BUNDLE and SSL_CERT_FILE env vars, and fix the CA cert volume mount path to use a generic system path (/etc/ssl/certs/local-ca.pem) instead of a Python-version-specific certifi path

Test plan

• Follow the updated guide on a fresh Kind cluster using bin/start-kind.sh
• Verify helm installs succeed with the corrected repo URLs
• Verify the backend trusts local certificates after populating the CA ConfigMap

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[alexandresib]

Hi everyone,
FYI I generated this PR with Claude.
I followed the contributing guide, all went well, except that Claude initially created only one commit for both the changes.

Consequently, I can suggest the following (you'll tell me if it's relevant or not):

• mention in the contributing guide the rules for the commits: maybe one type of change per commit or something like that?
• add a CLAUDE.md file on the repo to explain to agents how the repo works and how agents should contribute: for ex, something like "always follow CONTRIBUTING.md when pushing PRs"?