fix(post-gen-hook): populate project.yml with more accurate details

[JonZeolla]

Contributor Comments

This fixes the generated .github/project.yml to have correct details about the generation of a repo.

Now it looks like this:

...
origin:
  template:
    branch: unknown
    commit hash: unknown

Previously it looked like this in my local testing:

origin:
  generated: true
  template:
    branch: main
    commit hash: ''

Pull Request Checklist

Thank you for submitting a contribution!

Please address the following items:

• If you are adding a dependency, please explain how it was chosen.
• If manual testing is needed in order to validate the changes, provide a testing plan and the expected results.
• Validate that documentation is accurate and aligned to any project updates or additions.

[ai-coding-guardrails]

I've got 2 comments for you to consider

The PR title and description are not accurate. Here are my suggestions:

Title: refactor(post-gen-hook): improve template handling and fix project.yml generation

Description: # Contributor Comments

This PR refactors the post-generation hook with several improvements:

Key Changes

• Template handling: Added distinction between remote and local templates for better context resolution
• Performance: Implemented lazy loading for git imports
• Code quality: Removed pylint disable comments and improved code structure
• Project metadata: Fixed generated .github/project.yml to populate correct details about repo generation

Project.yml Improvements

The generated project metadata now includes proper template information with fully qualified paths instead of local development paths.

Previously the generated file contained local paths like:

_template: /Users/jonzeolla/src/zenable/testing
location: /Users/jonzeolla/src/zenable/testing

Now it properly reflects the actual template source and generation context.

Pull Request Checklist

• If you are adding a dependency, please explain how it was chosen.
• If manual testing is needed in order to validate the changes, provide a testing plan and the expected results.
• Validate that documentation is accurate and aligned to any project updates or additions.

Reviewed with 🤟 by Zenable