feat(integrations): Advanced GitHub Projects write support and Issue Templating parity

This issue tracks the implementation of advanced automation tools for GitHub and Codeberg, specifically focusing on Project management and Issue Templating.

1. GitHub Projects v2 (Write Support)

Currently, the GitHub integration only supports basic listing/reading of projects. We need first-class write automation:

• add_item_to_project: Add issues or PRs to a project.
• set_project_field_value: Update fields (Status, select options, dates, etc.).
• move_project_item: Explicit tool for moving items between columns/views.
• list_project_items: Enhanced listing with filtering by status/assignee.
• archive_project_item / delete_project_item.

2. Issue Templating (GitHub & Codeberg)

To support modern "create issue" workflows, we need to handle repository-level templates:

• list_issue_templates: Discover .github/ISSUE_TEMPLATE/*.yml (GitHub) or .forgejo/ISSUE_TEMPLATE/*.yml (Codeberg).
• get_issue_template: Parse template fields, metadata (labels, assignees), and "about" info.
• create_issue_from_template: A high-level tool that:
  • Renders the body from template fields.
  • Automatically applies labels/assignees defined in the template.
  • Optionally ensures labels exist (auto-creation policy).

Goals

• Enable AI agents to respect repository standards when opening issues.
• Support full project board automation for CI/CD and triage workflows.

See memory context be274c1b-8e40-498d-b87f-0bcd24cfc1c3 for original proposal details.

Start by locating the existing GitHub integration entry points for project listing and reading. Inspect the repository template paths .github/ISSUE_TEMPLATE/*.yml and .forgejo/ISSUE_TEMPLATE/*.yml, then map the requested project-management and template operations to the current integration structure. Done means the listed GitHub Projects write tools and GitHub/Codeberg template workflows are implemented with their stated filtering, rendering, metadata, and label behavior.