Simplify action.yml to use rhiza's default .github/template.yml convention

[Copilot]

The rhiza tool expects .github/template.yml by convention and operates on the repository root. The previous implementation incorrectly accepted a custom source path and passed a file path to rhiza instead of the repository root.

Changes:

• Removed inputs.source parameter - rhiza uses .github/template.yml by default
• Fixed rhiza command invocation to pass repository root (.) instead of file path
• Removed CONFIG_FILE variable and file copying logic from action steps
• Updated test to create .github/template.yml in correct location

Before:

inputs:
  source:
    description: 'Path to the template file'
    required: false
    default: 'template.yml'
steps:
  - name: Validate Template
    run: rhiza validate ${{ env.CONFIG_FILE }}

After:

steps:
  - name: Validate Template
    run: rhiza validate .

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)