feat: copilot files (instructions and setup steps)

This ensures that when we have the copilot agent writing PRs, it sets up its environment correctly and understands our standards for coding.

- Copilot Instructions file ([docs](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/agents/copilot-coding-agent/best-practices-for-using-copilot-to-work-on-tasks#adding-custom-instructions-to-your-repository))
- Copilot Setup Steps ([docs](https://docs.github.com/en/copilot/how-tos/agents/copilot-coding-agent/customizing-the-development-environment-for-copilot-coding-agent#preinstalling-tools-or-dependencies-in-copilots-environment))

Already added to [Evergreen](github/evergreen#382)

Signed-off-by: jmeridth <[email protected]>

Author: jmeridth

.github/copilot-instructions.md

@@ -0,0 +1,30 @@
+# Copilot Instructions
+
+This is a GitHub Action that given an organization or specified repositories, produces information about the [contributors](https://chaoss.community/kb/metric-contributors/) over the specified time period.
+
+## Code Standards
+
+### Required Before Each Commit
+
+- Run `make lint` before committing any changes to ensure proper code linting and formatting.
+
+### Development Flow
+
+- Lint: `make lint`
+- Test: `make test`
+
+## Repository Structure
+
+- `Makefile`: Contains commands for linting, testing, and other tasks
+- `requirements.txt`: Python dependencies for the project
+- `requirements-test.txt`: Python dependencies for testing
+- `README.md`: Project documentation and setup instructions
+- `setup.py`: Python package setup configuration
+- `test_*.py`: Python test files matching the naming convention for test discovery
+
+## Key Guidelines
+
+1. Follow Python best practices and idiomatic patterns
+2. Maintain existing code structure and organization
+3. Write unit tests for new functionality.
+4. Document changes to environment variables in the `README.md` file.

.github/workflows/copilot-setup-steps.yml

@@ -0,0 +1,38 @@
+name: "Copilot Setup Steps"
+
+# Automatically run the setup steps when they are changed to allow for easy validation, and
+# allow manual testing through the repository's "Actions" tab
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+  pull_request:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+
+# Set the permissions to the lowest permissions possible needed for your steps.
+# Copilot will be given its own token for its operations.
+permissions:
+  # If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
+  contents: read
+
+jobs:
+  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
+  copilot-setup-steps:
+    runs-on: ubuntu-latest
+
+    # You can define any steps you want, and they will run before the agent starts.
+    # If you do not check out your code, Copilot will do this for you.
+    steps:
+      - name: Checkout code
+        uses: actions/[email protected]
+
+      - name: Set up Python
+        uses: actions/[email protected]
+        with:
+          python-version: 3.12
+
+      - name: Install dependencies
+        run: |
+          pip install -r requirements.txt -r requirements-test.txt