Add translation guidelines and issue template

[suryabdev]

More details discussed in #1810

This PR adds guidelines to translate the documentation and a corresponding github issue template

[aymeric-roucher]

Thank you, that seems very clear!

[suryabdev]

PR quality check failed with errors unrelated to this PR. Those should be fixed in #1809. Merged this branch with main
@aymeric-roucher Thanks for the review, Please re-trigger the checks when you are free

[albertvillanova]

Thanks! Some comments/suggestions/questions below.

[albertvillanova]

For consistency with the rest of the docs, I would recommend to use the ASCII character for the apostrophe through all the docs:

Suggested change

	4. Post a comment indicating which chapters you’d like to work on, and we’ll add your name to the list.
	4. Post a comment indicating which chapters you'd like to work on, and we'll add your name to the list.

There are other cases in this PR.

[suryabdev]

Replaced all non ASCII apostrophes in TRANSLATING.md, intro_agents.md and text_to_sql.md

[albertvillanova]

Instead of removing unrelated section, I would recommend commenting out them: this will prevent Git merge conflicts when adding the translation of other sections in other PRs. Note that many users contributing to docs might not have the technical skills to resolve Git merge conflicts, so better avoiding them.

Maybe something like:

Suggested change

	- If the `_toctree.yml` file doesn't exist for your language, create one by copying the English version and removing unrelated sections.
	- Ensure it is placed in the `docs/source/LANG-ID/` directory.
	- If the `_toctree.yml` file doesn't exist for your language, create one by copying the English version and commenting out unrelated sections (instead of deleting them) to avoid potential merge conflicts with other PRs.
	- If the `_toctree.yml` file already exists for your language, open it and uncomment the sections that apply to the chapter you're translating.
	- Ensure it is placed in the `docs/source/LANG-ID/` directory.

[suryabdev]

Good point! It will make it easier for documentation contributors

[albertvillanova]

Suggested change

	2. Once you’ve translated the `_toctree.yml`, move on to translating the associated MD files.
	2. Once you've set up and translated the `_toctree.yml`, proceed to translate the associated Markdown (`.md`) files.

[albertvillanova]

I think we should locate the TRANSLATING.md file at the root of the repo, what do you think?

[suryabdev]

I copied the file location from the transformers repo (/docs)
One reason for them placing it in the docs folder could be that all documentation and instructions for contributing to the docs are located there. (e.g., /docs/README.md). So it is an intuitive location, but I don't have any strong opinions. I’m fine with moving it to the root of the repository if that’s what you prefer.

[albertvillanova]

Not sure about personalizing the tag. What about something more general like:

Suggested change

	If you'd like assistance with your translation, open an issue and tag `@albertvillanova`. Feel free to share resources or glossaries to ensure consistent terminology.
	If you'd like assistance with your translation, open an issue and tag the documentation maintainers. Feel free to share resources or glossaries to ensure consistent terminology.

[suryabdev]

Copied it from the transformers repo, I think they have a dedicated documentation maintainer
https://github.com/huggingface/transformers/blob/main/docs/TRANSLATING.md#collaborate-and-share
Changed it to maintainers in this PR

[suryabdev]

@albertvillanova Thanks for the review. I've made the suggested changes. I have one clarification, Please take a look when you are free