Add Dev_cycle_2 work package and interface issue forms

[BotshareAI]

Summary

Add two organization-level issue forms to make Dev_cycle_2 work traceable and reviewable:

• .github/ISSUE_TEMPLATE/work_package.yml
• .github/ISSUE_TEMPLATE/interface_change_request.yml

Plan alignment

• D-03: creates a consistent work-package and interface-change intake path.
• Q-01: asks for acceptance evidence, compatibility classification, consumer impact, and truthful readiness claims.
• D-01: directs implementation-sensitive facts to the owning repository and requires affected documentation to be identified.

Scope

This PR changes issue intake only. It does not change source code, ROS interfaces, workflows, labels, milestones, rulesets, branch protection, or repository structure.

The forms are limited to maintained-repository work in the current Dev_cycle_2 cycle. Archived repositories, the legacy openamr monorepo, and unrelated future-cycle orchestration topics are intentionally excluded. Open-RMF is not introduced in this cycle.

Validation

• Confirmed both new files exist on the branch.
• Confirmed the existing issue-template configuration is unchanged.
• Repository quality workflow passed for the PR.
• No runtime, interface, safety, or readiness behavior is changed.

Readiness impact

None. This is governance and planning infrastructure only.