Docs: Add supported languages for Chrome Translator API

[gswetha]

This document lists the languages supported by Chrome's Translator API, including codes and language names.

[tomayac]

LGTM with formatting nits.

[tomayac]

Suggested change

	The following languages are currently supported by Chrome's implementation of the Translator API.
	The following languages are currently supported by Chrome's implementation of the Translator API.

[tomayac]

Suggested change

<table>

<tr>

As per https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables#creating-a-table, this is enough:

| First Header  | Second Header |
| ------------- | ------------- |
| Content Cell  | Content Cell  |
| Content Cell  | Content Cell  |

[tomayac]

Suggested change

	</tr>
	</table>

See comment above.

[anssiko]

Thanks for this contribution! Could we turn this into "impl-status.md" to be more inclusive of other implementers? For example, Translator API in Edge may support a different set of languages.

[gswetha]

Thank you! I've renamed the file.

[anssiko]

Maybe sectioning like this works better:

# Implementation Status

## Translator API

### Chrome

#### Supported Languages

... table here ...

### Edge

...

## LanguageDetector API

...

@tomayac I think the ultimate destination for this information might be https://github.com/mdn/browser-compat-data from where caniuse.com and others pulls their data. Not sure if BCD schema supports this tabular format though.

Paging @Elchi3 for advice. We're trying to figure out where to host more detailed implementation status information that go beyond the usual schema. See this PR.

[tomayac]

That's a good point. A natural destination might also be https://developer.mozilla.org/en-US/docs/Web/API/Translator/translate.

We have a similar list of supported items in https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share#shareable_file_types, but without mentioning concrete browsers, though the list was definitely driven by people not knowing what could be shared.

[Elchi3]

Paging @Elchi3 for advice. We're trying to figure out where to host more detailed implementation status information that go beyond the usual schema. See this PR.

Some prior art for this might be the CSS hyphens property which essentially uses a lot of sub features.
MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/hyphens#browser_compatibility
BCD: https://github.com/mdn/browser-compat-data/blob/main/css/properties/hyphens.json

[anssiko]

@gswetha, please investigate if this supported language information fits within the BCD schema. See the example above. If that works, I recommend you contribute this data to BCD, see https://github.com/mdn/browser-compat-data/blob/main/docs/contributing.md