chore: update charm-ci to v0.0.1-alpha.10

[javierdelapuente]

What this PR does

Upgrade charm-ci

Why we need it

Checklist

• Changes comply with the project's coding standards and guidelines (see CONTRIBUTING.md and STYLE.md)
• CONTRIBUTING.md has been updated upon changes to the contribution/development process (e.g. changes to the way tests are run)
• Technical author has been assigned to review the PR in case of documentation changes (usually *.md files)
• I updated docs/changelog.md with user-relevant changes
• I used AI to assist with preparing this PR
• I added or updated tests as needed (unit and integration)
• If integration test modules are used: I updated the workflow configuration
  (e.g., in .github/workflows/integration_tests.yaml, ensure the modules list is correct)
• If this PR involves a Grafana dashboard: I added a screenshot of the dashboard
• If this PR involves Terraform: terraform fmt passes and tflint reports no errors
• If this PR involves Rockcraft: I updated the version
• If this PR adds/removes a charm, or changes a charm's base class, conventions, tooling, or repo structure: I updated the relevant AGENTS.md
• If this PR changes .copilot-collections.yaml or .github/instructions/: I re-checked whether the AGENTS.md "12-factor divergences" guidance still matches the upstream copilot-collections guidance

[yhaliaw]

Pins the two canonical/charm-ci reusable-workflow refs from floating @main to the tag @v0.0.1-alpha.10, which resolves to the same commit as charm-ci's current main (0 ahead/0 behind), so this carries no unreviewed drift. All with: inputs and permissions: blocks still match what the reusable workflows require at that tag.

One gap worth a look before merging: this only pins 2 of the 4 charm-ci/opcli references in the repo.

• tox.ini:106 — opcli @ git+https://github.com/canonical/charm-ci.git@main is still floating on @main, so the *-integration tox envs can drift from the now-pinned CI workflows.
• spread.yaml:16 — OPCLI_GIT_REF still defaults to main ('$(HOST: echo "${OPCLI_GIT_REF:-main}")'), so spread runs without an explicit override keep pulling from main.

Prior precedent (1ab0b6e / PR #270) pinned all four sites together and was approved specifically for that consistency. Worth bumping these two alongside the workflow files, or noting in the description if leaving them floating is intentional this round. Neither blocks approval since the change as scoped is correct.

---

🤝 Human review with AI assistance.