Add some information on must haves in a PR description.

Right now, a lot of PRs contain only information about the changes being made like "Add foo module" but not enough context around the change. Ideally, a PR should contain more information as described in the changes below to make for easier/better reviews as well as for historical reference.

Tested the formatting by looking at the rendered markdown on github.
@MaerF0x0 we have them enabled! If you put the JIRA key (e.g. API-56) in the branch name it will be linked in the JIRA ticket.