[Issue] Modified the PR template to include README.md update reqirement if necessary

[m2-assistant]

This issue is automatically created based on existing pull request: #32610: Modified the PR template to include README.md update reqirement if necessary

---

Description (*)

With the introduction of the README.md template, there is a requirement of describing module installation, structure and extension points in the readme.
We need to pay special attention to README.md always being up to date, because an outdated readme can do more harm than good. This is why all code contributors need to be aware that they are supposed to modify README.md as well when they create modifications that affect any of readme predefined sections.

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

1. Attempt to create a Pull Request to this or any other github repository
2. When on the PR edit page, copy-paste the modified template content into your PR description area
3. Click Preview
4. Along the Contribution checklist checkboxes you should see a new checkbox with a description saying that README.md needs to be modified if necessary
5. Well, check if it looks beautiful :)
6. Don't create that PR as you don't need to, unless you want to check that the markdown looks the same on an actual PR as in the Preview window

Questions or comments

Contribution checklist (*) - THIS SECTION CONTAINS THE CHECKBOX THAT I ADDED

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

✅ Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-41715 were created

Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[gabrieldagama]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #32610 by @bgorski in 2.4-develop branch
Related commit(s):

• 4a7159e43f24068f7aca856412d6376a81e1721c
• ef7009ea0781862e3ca54ed1564058db0e9baa55

The fix will be available with the upcoming 2.4.3 release.