I was a bit confused by the new PR template, so I'm proposing some change to PR template. Please let me know if that make sense.
## Azure IoT Edge PR checklist:
This commit adds a rule to the kodiakhq bot to remove the PR template from the commit body when a PR is merged.
There were no tests added or modified. Also, there was no local testing done as a PR merge is needed to check if it is working as intended.
# Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
### General Guidelines and Best Practices
- [x] I have read the [contribution guidelines](https://github.com/azure/iotedge#contributing).
- [x] Title of the pull request is clear and informative.
- [x] Description of the pull request includes a concise summary of the enhancement or bug fix.
### Testing Guidelines
- [x] Pull request includes test coverage for the included changes.
- Description of the pull request includes
- [x] concise summary of tests added/modified
- [x] local testing done.
### Draft PRs
- Open the PR in `Draft` mode if it is:
- Work in progress or not intended to be merged.
- Encountering multiple pipeline failures and working on fixes.
_Note: We use the kodiakhq bot to merge PRs once the necessary checks and approvals are in place. When it merges a PR, kodiakhq converts the PR title to the commit title, PR description to the commit description, and squashes all the commits in the PR to a single commit. The net effect is that entire PR becomes a single commit. Please follow the best practices mentioned [here](https://chris.beams.io/posts/git-commit/#:~:text=The%20seven%20rules%20of%20a%20great%20Git%20commit,what%20and%20why%20vs.%20how%20For%20example%3A%20) for the PR title and description_
This commit adds a checklist for PR authors to follow. This initial rev of the PR checklist contains general documentation, testing guidelines, and points PR authors to our contribution guidelines.