feat(run): add support for private CA trust with containerd certs management

[NFRBEZ]

Signed-off-by: Nicolas nicolas.frbezar@decathlon.com

Description of your changes

This PR adds support for mounting a host containerd certs directory into the local development control-plane node created by crossplane project run.

Main changes:

• Added a new --containerd-certs-dir flag to crossplane project run.
• Mounted the provided host directory into /etc/containerd/certs.d when creating a new Kind control plane.
• Updated project run help documentation to clarify:
  • the path must be a containerd certs.d-style directory tree,
  • hosts.toml is optional,
  • _default fallback usage,
  • reference to containerd docs for registry host configuration.

Validation:

• Ran targeted checks on changed packages: go test ./internal/project/controlplane ./cmd/crossplane/project
• Updated command help documentation accordingly.

Closes #97

I have:

• Read and followed Crossplane's contribution process.
• Run ./nix.sh flake check to ensure this PR is ready for review.
• Added or updated unit tests.
• Linked a PR or a docs tracking issue to document this change.
• Added backport release-x.y labels to auto-backport this PR.

Need help with this checklist? See the cheat sheet.

[adamwg]

Thanks for the contribution, @NFRBEZ! This looks like a valuable feature. Is this PR waiting for anything before being marked as ready for review?

One initial thought: rather than adding a specific flag for the certs directory, could we add a flag to specify a kind config and/or the ability to customize the dev control plane (both kind config and helm values) in the crossplane-project.yaml file? That would solve this use-case and also avoid the need for more updates and more flags to support other kind options.