chore: create pull request template

[gfellerph]

📄 Description

This PR adds a pull request template that will be used to prefill the body of each pull request. The goal is to create pull requests that are easier to review because the reviewer gets all the information necessary before digging into the code

🚀 Demo

## 📄 Description

Please include a summary of the changes made in this PR.

## 🚀 Demo

If applicable, please add a screenshot or video to illustrate the changes.

---

## 📝 Checklist

- ✅ My code follows the style guidelines of this project
- 🛠️ I have performed a self-review of my own code
- 📄 I have made corresponding changes to the documentation
- ⚠️ My changes generate no new warnings or errors
- 🧪 I have added tests that prove my fix is effective or that my feature works
- ✔️ New and existing unit tests pass locally with my changes

---

📝 Checklist

• ✅ My code follows the style guidelines of this project
• 🛠️ I have performed a self-review of my own code
• 📄 I have made corresponding changes to the documentation
• ⚠️ My changes generate no new warnings or errors
• 🧪 I have added tests that prove my fix is effective or that my feature works
• ✔️ New and existing unit tests pass locally with my changes

[changeset-bot]

⚠️ No Changeset found

Latest commit: d021baf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alizedebray]

Is this necessary? The ticket is usually available in the right column under "Development":

[alizedebray]

We have the preview link for that, no?

[gfellerph]

yes, but a screenshot or a video really helps to illustrate the change fast so you don't have to go hunt for what could possibly have changed based on the source. I'd like to keep that point.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud