besu/.github/pull_request_template.md

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines 
https://github.com/PegaSysEng/pantheon/blob/master/CONTRIBUTING.md#your-first-code-contribution
2. Label the PR appropriately how to mark it: 
https://github.com/PegaSysEng/pantheon/blob/master/CONTRIBUTING.md#pull-request-labels
-->

## PR description

<!--- Describe your changes in detail, including motivation and context -->

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #

## Related Issue(s)

<!--- Please link to related issue(s) here: -->

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->

- [ ] Docs change / refactoring / dependency upgrade
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

## Release note
<!--  Write your release note:
1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
2. If no release note is required, just write "NONE".
-->
```release-note

```

## Prerequisites:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] I have read the **CONTRIBUTING.md** document and followed the guidelines there.
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have opened an issue for corresponding changes to documentation (OR no doc changes required)
- [ ] I have added appropriate tests that prove my change is effective