Simplify user description issue template

[nvborisenko]

User description

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Documentation

---

Description

• Simplified the pull request template for contributors.

• Removed redundant sections to streamline the process.

---

Changes walkthrough 📝

	Relevant files
Documentation	PULL_REQUEST_TEMPLATE.md Simplified the pull request template structure                      .github/PULL_REQUEST_TEMPLATE.md Removed the Description section from the template. Retained the Motivation and Context section for clarity. Simplified the template to focus on essential details. +0/-4

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.

[nvborisenko]

Each time when I create PR, the description is duplicated:

So may be just remove extra description section from template?