[Feature] Auto-discover CRDs from repository root URL

### Current Behavior

Currently, the model generator requires users to point to a specific directory inside of a repo to locate CustomResourceDefinitions (CRDs). This makes the source location brittle; if the repo structure changes, the generator fails.

### Desired Behavior

We need to make the location we use as the source of CRDs more robust.

Users should be able to simply point to a repository URL (e.g., https://github.com/crossplane/crossplane), and the component generator should automatically find the CRDs from there, regardless of where they are located in the file structure.

### Implementation
Use the logic in [crdsdev/doc](https://github.com/crdsdev/doc) as inspiration for enhancing the discovery mechanism in MeshKit. The goal is to move away from static directory paths to a more robust discovery method.