docs(language): Enforce English on contributions and issues

[lucasssvaz]

This pull request introduces updates to enforce English as the standard language for communication in feature requests, issue reports, and contributions. These changes aim to ensure effective communication and streamline the review process.

Updates to communication guidelines:

• .github/ISSUE_TEMPLATE/Feature-request.yml: Added a note specifying that feature requests must be written in English. Requests in other languages will be closed with a request to rewrite them in English.
• .github/ISSUE_TEMPLATE/Issue-report.yml: Added a similar note for issue reports, requiring them to be submitted in English for effective processing.

Updates to contribution guidelines:

• docs/en/contributing.rst: Introduced a new guideline stating that all contributions, including pull requests, must be written in English. Contributions in other languages will be closed with a request for re-submission in English.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 0741e27

[pedrominatel]

LGTM