Another question: my team is working on creating a git-based development workflow using a self-hosted prefect server on our kubernetes cluster. Due to the sheer number of different "projects" or "jobs" we want to group multiple prefect projects into one repo. Here's an example structure:

git-repo-name/
      project1/
           flow.py
           requirements.txt
      project2/
           flow.py
           requirements.txt

Would it be best to initialize each project subdirectory as a prefect project with it's own prefect.yaml and deployment.yaml, or have it in the root directory and configure different deployments to use the different subdirectories. We also want to isolate dependencies for each project subdirectory in it's own container, so this will also have to influence the architecture of this development workflow. The configuration for each project subdirectory's deployment will be fairly similar, so what would you all suggest as the cleanest way to initialize for example a project 3? Is there some way to make "custom recipes" that can be used in prefect project init --recipe recipeName or is there a different solution such as using yaml aliases