Cicd/labeler hard code config files as content

[JMielbrecht]

Fixes #102

Guidelines and Checklists (click to expand)

📝 Guidelines for Philosophical/Literary Contributions

License Agreement

By submitting this PR, you agree to license your content under the
CC BY-NC-SA 4.0 License.

Required Steps

1. Follow the
   formatting guidelines
2. Use
   Chicago author-date style
   for citations
3. Update the
   project's central bibliography
4. Add metadata at the top of your file:

---
title: Your Title Here
description: Brief description of your content
isArticle: true
authors: Your Name (Year)
editors: Editor Name (Year)
contributors: Contributor Name (Year)
---

## Your Article Title

Optional

Consider adding the Stub component to encourage further contributions.

💻 Guidelines for Code Contributions

Required Steps

1. Ensure code adheres to project coding standards
2. Thoroughly test all changes

License Scope

The Apache License 2.0 applies to all code except content within content/**
folder (excluding /contributing/**, _meta.ts, acknowledgements.mdx,
index.mdx, privacy.mdx, team.mdx, terms.mdx). This primarily covers
technical implementations rather than content, literature, or philosophy.

ℹ️ Additional Information

• Philosophical/literary content: Licensed under CC BY-NC-SA 4.0
• Code contributions: Licensed under Apache License 2.0
• Please sign your contribution in the metadata under Authors, Editors, or
  Contributors

License Agreement

By submitting this PR, you agree to license your content under the
CC BY-NC-SA 4.0 License
and your code under the
Apache License 2.0.

[Firgrep]

I see that the labeler fails if the PR is coming from a remote codebase (forked). I think it was the same issues we had with prettier. If this can't be solved within the workflow, we can move this logic to autogit since it doesn't have the same constraints.