chore: add issue templates (#1105)

* chore: add issue templates

These are the auto-generated templates for feature requests/bug reports

* Revise bug report template structure and content

* Create pull request template

* Update feature request template

---------

Co-authored-by: isc-dchui <dchui@intersystems.com>

Author: isc-tleavitt

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Create a report to help us improve
+labels: 'bug'
+
+---
+
+## Describe the bug
+A clear and concise description of what the bug is.
+
+## To Reproduce
+Steps to reproduce the behavior:
+1. Run IPM command '...'
+2. Run another IPM command '...'
+3. See error
+
+## Expected behavior
+A clear and concise description of what you expected to happen.
+
+## Screenshots
+If applicable, add screenshots to help explain your problem.
+
+## System information (please complete the following information):
+ - IPM version: [e.g. 0.10.6]
+ - IRIS version: [e.g. output of $zversion]
+ - OS: [e.g. Unix, Windows]
+ - Docker or local:
+
+## Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+labels: 'enhancement'
+
+---
+
+## Link to the discussion thread
+Have you started a discussion thread about this feature request? If not, do that first.
+<!-- If you do not yet have approval from IPM's maintainers, add the "Needs Spec" label to this issue. -->
+
+## Describe the problem
+A clear and concise description of what the problem is.
+
+## Describe the solution
+A clear and concise description of what you want to happen.
+
+## Describe alternatives
+A clear and concise description of any alternative solutions or features you've considered.
+
+## Additional context
+Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -0,0 +1,17 @@
+## Description
+- Link the issue using the [magic closing words](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue).
+- Provide a summary of the change and how it addresses the issue (e.g. if it is a bug, explain the root cause of the bug and how this change fixes it).
+- Include any other necessary context, especially if any section warrants special reviewer attention.
+
+## Testing
+How has this change been tested? Have you added unit or integration tests as appropriate?
+
+## Checklist
+<!-- You can select a checkbox by changing "[ ]" to "[x]" -->
+- [ ] This branch has the latest changes from the `main` branch rebased or merged.
+- [ ] Changelog entry added.
+- [ ] Unit (`zpm test -only`) and integration tests (`zpm verify -only`) pass.
+- [ ] Style matches the style guide in the [contributing guide](https://github.com/intersystems/ipm/blob/main/CONTRIBUTING.md#style-guide).
+- [ ] Documentation has been/will be updated
+  - Source controlled docs, e.g. README.md, should be included in this PR and Wiki changes should be made after this PR is merged (add an extra issue for this if needed)
+- [ ] Pull request correctly renders in the "Preview" tab.