Update PR description template

[dhriaznov]

🔘 PR Type

What kind of change does this PR introduce?

• Bugfix
• Enhancement
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no API changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

📜 Background

Provide a brief explanation of why this pull request is needed. Include the problem you are solving or the functionality you are adding. Reference any related issues.

Issue Link: #[issue_number]
Context Link (if applicable): https://discord.com/channels/895889501560377364/938114005178916945/1116750424486187038

🔄 Changes

Enumerate the changes made in this pull request, detailing what has been modified, added, or removed. Include technical details and implications if necessary.

Impact:

• Explain the broader impact of these changes.
• How it improves performance, fixes bugs, adds functionality, etc.

🖼 Screenshot / 📹 Video

Include screenshots or a video demonstrating the changes. This is especially helpful for UI changes.

✅ Review checklist

Please ensure the following are true before merging:

• Code Style is consistent with the project guidelines.
• Code is readable and well-commented.
• No unnecessary or debugging code has been added.
• Security considerations have been taken into account.
• The change has been manually tested and works as expected.
• Breaking changes and their impacts have been considered and documented.
• Code does not introduce new technical debt or issues.

[victorkirov]

Would be good if we could also add what effect this could have within the service so that we think about and document what parts need to be QA'd in case of side effects.

[victorkirov]

This looks great 👍 If we make the effort to fill this out with meaningful info, I think we would have a good, self-documenting history of changes.