PR template readability and standardization fixes

[CodinGeo]

Pull Request (PR) Checklist

Please check if your pull request fulfills the following requirements:

• [✅] The PR is submitted to the main branch.
• [✅] I've read the Contribution Guidelines and my PR doesn't break the rules.
• [✅] I've read and understand the Developer Guidelines.
• [✅] I confirm that I've run the code locally and everything works as expected.
• 🎬 I've attached a screen recoding of the changes.
• [✅] My PR includes only the necessary changes to fix the issue (i.e., no unnecessary files or lines of code are changed).

What's changed?

Overall preview look:

Before	After

Describe with a few bullets what's new:

• Changed proposed way of ticking checkboxes (to the way I did it here above) - more stands out especially in the dark mode, but I can bring back the previous normal checkbox style:

Before	After

• Moved screen recording checkbox to last position for it to be next to the next paragraph to put this screen recording
• Emphasised the need of screen recording of changes in use in one of the paragraphs (visible in the first pair of screenshots)
• Made tips as comments, not this style
• Made markdown table easy to use to showcase changes made:

Before	After

• Changed a,b,c as placeholders to ...
• Automated PR - issue assigning simplified

Before	After

Risk Factors

What may go wrong if we merge your PR?

• It's a doc

In what cases your code won't work?

• It's a doc (have a nice day to anyone reading this)

Does this PR closes any GitHub Issues?

Check Ivy Wallet Issues.

• Closes Change UX of PR template #3313

Troubleshooting CI failures ❌

GitHub Actions failing? Read our CI Troubleshooting guide.

[ILIYANGERMANOV]

Looks good - left some comments