Add Issue and Pull Request Templates

Add Issue Templates and Pull Request Templates.
See below for reasons to have them.

Benefits of GitHub Issue Templates
Issue templates standardize the process for reporting bugs or requesting new features, ensuring that contributors provide all necessary information from the start.

• Consistency and Clarity: Templates enforce a standard format for issue submission, making them easier to read, prioritize, and manage.
• Faster Triage: By requiring specific details (e.g., steps to reproduce a bug, expected behavior), templates help maintainers quickly understand the problem without needing to ask follow-up questions
• Reduced Back-and-Forth: The guided structure minimizes the time wasted on communication loops, allowing the team to focus on resolving the issue faster.
• Improved Quality of Reports: Templates can include checklists, required fields, and guidance that prompt reporters to include necessary context, system information, or screenshots, leading to higher quality and more actionable reports.
• Onboarding and Guidance: They act as a form of documentation, guiding new contributors on the appropriate way to report issues in your specific repository.

Benefits of GitHub Pull Request Templates
PR templates provide a structured framework for submitting code changes, facilitating thorough and efficient code reviews.

• Streamlined Code Reviews: Templates ensure authors provide crucial information like a summary of changes, testing instructions, and related issues, enabling reviewers to understand the context and intent quickly.
• Enforce Best Practices: They can include reminders or checklists for essential development tasks, such as running tests, updating documentation, or checking for breaking changes.
• Better Communication: Templates standardize how changes are communicated, ensuring everyone involved in the review process has the same information and focus points.
• Increased Efficiency: By clearly outlining the purpose of a PR and what needs to be reviewed, templates speed up the review and merge process, reducing bottlenecks.
• Documentation and Traceability: The structured information within a merged PR serves as valuable historical documentation of the codebase's evolution and decisions made.

No files or tests are named. Start by reviewing the repository's current contribution and issue-reporting workflow, then define issue templates for bug reports and feature requests plus a pull request template covering the stated review information. Done means all requested templates are present and guide contributors to provide the necessary context.