refactor: Change the formatting of the community PR message to make it tighter

[xitij2000]

The current message is too spaced out, this change fixes the spacing issues and moves the hr to the correct place.

The h3 and h4 have been removed since they add too much spacing around in the collapsable and make the message seem too spaced out. Being inside a collapsable section already highlights them quite a bit so I'm hoping this is okay.

Screenshot after update:

[openedx-webhooks]

Thanks for the pull request, @xitij2000!

This repository is currently maintained by @feanil.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.72%. Comparing base (a68311a) to head (9824556).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #339   +/-   ##
=======================================
  Coverage   89.72%   89.72%           
=======================================
  Files          38       38           
  Lines        3026     3026           
  Branches      229      229           
=======================================
  Hits         2715     2715           
  Misses        279      279           
  Partials       32       32           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[itsjeyd]

Thanks @xitij2000, this looks great 👍

[itsjeyd]

Hey @feanil, this is just a small follow-up for openedx/wg-coordination#147, would you mind giving it a quick look?

[feanil]

@xitij2000 this needs a rebase but then I can merge and deploy it.

[xitij2000]

Not sure why the test are failing here. Doesn't seem to be related to the changes, but I'll have a closer look later.

[xitij2000]

I've hopefully fixed the test issues.

[itsjeyd]

@xitij2000 I came here again today as part of my weekly OSPR management pass and saw that the build was green but the branch had fallen out of date with the base branch again. So to speed things up I figured I'd merge in the latest changes from master myself, wait for the build to pass, and ping Feanil for review again. Unfortunately the merge seems to have (re-)introduced a test failure. Sorry about that! Could you please have a look when you get a minute?

[xitij2000]

@itsjeyd No worries! I just needed to drop my commit with the temporary fix.

[itsjeyd]

@xitij2000 Ah OK 😅 That's great.

@feanil We got a green build here now, could you please merge this PR? That'll wrap up openedx/wg-coordination#147.

[feanil]

The update is now deployed. Thanks @xitij2000