feat(project): add KinD configuration options and DinD support

[nkzk]

Description of your changes

This PR adds support for running crossplane project in devcontainers and closed company networks with the following changes:

1. Add configuration options for KinD in crossplane-project.yaml.

   • Allow the user to specify their own kind-config (to avoid the need for more updates and flags to support other kind options later, ref. Adam's comment in this issue)
   • Add options to:
     • specify docker-network
     • use internal KinD kubeconfig.
     • specify registry storage type (ref explanation below)
   Example crossplane-project file

    apiVersion: dev.crossplane.io/v1alpha1
    kind: Project
    metadata:
      name: example
    spec:
      dependencies:
        - type: xpkg
          xpkg:
            apiVersion: pkg.crossplane.io/v1
            kind: Function
            package: xpkg.crossplane.io/crossplane-contrib/function-go-templating
            version: "v0.12.4"
        - type: xpkg
          xpkg:
            apiVersion: pkg.crossplane.io/v1
            kind: Provider
            package: xpkg.crossplane.io/crossplane-contrib/provider-kubernetes
            version: "v1.3.1"
      repository: example.com/my-org/example
     # New runtime field 
      runtime:
        registry:
          storage:
            type: volume
        kind:
          config:
            path: kind-config.yaml
          internal: true
          network:
            name: my-network

2. Support registry data sideloading when running crossplane project in Docker-in-Docker

   When running crossplane project in a container, bind-mounting the CLI’s local registry directory into the registry container mounts an empty host path, leaving the registry without its certificates and package data.
   This happens because the generated files are only in the container where the command was ran, and not on the host.

   I added a storage interface where the bind-mount implementation ensures we keep old behavior, and a config-flag to use a volume-implementation. This required some refactoring of the code, for example where certs are created.

Fixes #313

With these changes, a user in a closed company network and devcontainer can run crossplane project with the following files and command:

./crossplane-project.yaml

apiVersion: dev.crossplane.io/v1alpha1
kind: Project
metadata:
  name: example
spec:
  dependencies:
    - type: xpkg
      xpkg:
        apiVersion: pkg.crossplane.io/v1
        kind: Function
        package: xpkg.crossplane.io/crossplane-contrib/function-go-templating
        version: "v0.12.4"
    - type: xpkg
      xpkg:
        apiVersion: pkg.crossplane.io/v1
        kind: Provider
        package: xpkg.crossplane.io/crossplane-contrib/provider-kubernetes
        version: "v1.3.1"
  repository: example.com/my-org/example
    runtime:
      registry:
        storage:
          type: volume
    kind:
      config:
        path: kind-config.yaml
      internal: true
      network:
        name: my-network

./kind-config.yaml

apiVersion: kind.x-k8s.io/v1alpha4
kind: Cluster
containerdConfigPatches:
  - |
    [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
        endpoint = ["https://docker-remote.my-registry.com"]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors."ghcr.io"]
        endpoint = ["https://ghcr-remote.my-registry.com"]

./image-configs.yaml

---
apiVersion: pkg.crossplane.io/v1beta1
kind: ImageConfig
metadata:
  name: docker.io
spec:
  matchImages:
    - prefix: docker.io
  rewriteImage:
    prefix: docker-remote.my-registry.com
---
apiVersion: pkg.crossplane.io/v1beta1
kind: ImageConfig
metadata:
  name:  ghcr.io
spec:
  matchImages:
    - prefix: ghcr.io
  rewriteImage:
    prefix: ghcr-remote.my-registry.com

crossplane project run --init-resources=image-configs.yaml

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.

[nkzk]

Before review, I want to refactor this again so that the registry-storage works like before by default, and add a config flag for the docker-volume method. I think that will be cleaner and better.