Add issue templates

[daogrady]

Add GitHub Issue Templates

New Feature

✨ Introduced structured GitHub issue templates to standardize how contributors report bugs, request features, and ask questions in the repository.

Changes

• .github/ISSUE_TEMPLATE/bug_report.yaml: Adds a bug report template with fields for current behavior, expected behavior, steps to reproduce (required), environment details (OS, Node, npm, @cap-js/asyncapi, cds versions), a link to a minimal reproducible example repository, and a free-form "Anything else?" section. Includes a duplicate-check checkbox.

• .github/ISSUE_TEMPLATE/feature_request.yaml: Adds a feature request template with required fields for description and suggested solution, plus optional fields for alternatives and additional context.

• .github/ISSUE_TEMPLATE/question.yaml: Adds a minimal question template with a single required text area for the question itself.

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.29.33

• Correlation ID: ba1d13c0-9d23-11f1-9dc9-cbee0cadaf17
• Summary Prompt: Default Prompt
• Event Trigger: pull_request.edited
• LLM: anthropic--claude-4.6-sonnet
• File Content Strategy: Full file content
• Output Template: Default Template

[hyperspace-pr-bot]

The most critical issue in this PR is that all three template files are placed in a top-level ISSUE_TEMPLATE/ directory instead of .github/ISSUE_TEMPLATE/, which means GitHub will silently ignore them and no template will ever appear when users open an issue. Additionally, the "Current Behavior" field in the bug report template is optional despite being essential information for triaging a bug.

PR Bot Information

Version: 1.29.33

• Correlation ID: 6ded4b00-9d23-11f1-8bb0-3d0298e5e9d5
• File Content Strategy: Full file content
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened