chore(xfer): update pull request template (#605)

Post-transfer update of pull request template.

Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>

Author: tenthirtyam

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,29 +1,105 @@
-**DELETE THIS PART BEFORE SUBMITTING**
+<!-- markdownlint-disable first-line-h1 no-inline-html -->
 
-In order to have a good experience with our community, we recommend that you
-read the contributing guidelines for making a PR, and understand the lifecycle
-of a Packer Plugin PR:
+<!--
+    NOTE: Do NOT enter content between the comment markers <!- and ->.
 
-https://github.com/hashicorp/packer-plugin-vsphere/blob/main/.github/CONTRIBUTING.md#opening-an-pull-request
+    In order to have the best experience with our community, we recommend that you read the code of
+    conduct and contributing guidelines before submitting a pull request.
 
-----
+    By submitting this pull request, you confirm that you have read, understood, and agreed to the
+    project's code of conduct and contributing guidelines.
 
-### Description
-What code changed, and why?
+    Please use conventional commits to format the title of the pull request and the commit messages.
 
+    For more information, please refer to https://www.conventionalcommits.org and the contributing
+    guidelines for this project.
+-->
 
-### Resolved Issues
-If your PR resolves any open issue(s), please indicate them like this so they will be closed when your PR is merged:
+### Summary
 
-Closes #xxx
-Closes #xxx
+<!--
+    Please provide a clear and concise description of the pull request.
+-->
 
-<!-- heimdall_github_prtemplate:grc-pci_dss-2024-01-05 -->
-### Rollback Plan
+### Type
 
-If a change needs to be reverted, we will roll out an update to the code within 7 days.
+<!--
+    Please check the one(s) that applies to this pull request using "x".
+-->
 
-### Changes to Security Controls
+- [ ] `fix`: Bug Fix
+- [ ] `feat`: Feature or Enhancement
+- [ ] `docs`: Documentation
+- [ ] `refactor`: Refactoring
+- [ ] `chore`: Build, Dependencies, Workflows, etc.
+- [ ] `other`: Other (Please describe.)
 
-Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
+### Breaking Changes?
 
+<!--
+    Please check the one that applies to this pull request using "x".
+    If this pull request contains a breaking change, please describe the impact and mitigation path.
+-->
+
+- [ ] Yes, there are breaking changes.
+- [ ] No, there are no breaking changes.
+
+### Tests
+
+<!--
+    Please check the one(s) that applies to this pull request using "x".
+    For bug fixes and enhancements/features, please ensure that tests and documentation have been completed and provide details.
+-->
+
+- [ ] Tests have been added or updated.
+- [ ] Tests have been completed.
+
+Output:
+
+<!--
+    Please provide the output of the acceptance tests as applicable.
+-->
+
+### Documentation
+
+<!--
+    Please check the one(s) that applies to this pull request using "x".
+    For enhancements/features, please ensure that documentation has been updated.
+-->
+
+- [ ] Documentation has been added or updated.
+
+### Issue References
+
+<!--
+    Is this related to any GitHub issue(s)? If so, please provide the issue number(s) that are closed or resolved by this pull request.
+
+    For bug fixes and enhancements/features, please ensure that a GitHub issue has been created and provide the issue number(s) here.
+
+    Please use the 'Closes', 'Resolves', or 'Fixes' keywords followed by a hash and issue number.
+    This will link the pull request to the issue(s) and automatically close them when the pull request is merged.
+
+    Example:
+
+    Closes #000
+    Resolves #001
+    Fixes #002
+-->
+
+### Release Note
+
+<!--
+    Please provide context for the release notes.
+
+    For example:
+
+    ```
+    - Added support for foo. (#xxx)
+    ```
+-->
+
+### Additional Information
+
+<!--
+    Please provide any additional information that may be helpful.
+-->