"isJapanese" check move

[toasted-nutbread]

Resolves #717.

This change generalizes how languages are checked to see if a string "may be translatable". This now supports additional languages, although it is only explicitly set up for Japanese at this point.

There are two functions worth noting:

• getLanguageFromText is used to determine which language a string "might" be using. This is only used for assigning a lang attribute on the generated content.
• textMayBeTranslatable is used to determine if the text might be translatable into that language. This is used to filter out things for the clipboard monitor as well as a lesser-used edge case of determining whether or not image alt text, button text, etc. should show the query parser in the standard search popup.

[codspeed-hq]

CodSpeed Performance Report

Merging #730 will not alter performance

_{Comparing toasted-nutbread:is-japanese-check-move (3f3cdc3) with master (73169f0)}

Summary

✅ 4 untouched benchmarks

[github-actions]

✔️ No visual differences introduced by this PR.

View Playwright Report (note: open the "playwright-report" artifact)

[StefanVukovic99]

Amazing, thank you 🙏

[djahandarie]

Two naming comments:

1. The first is kind of unrelated to the change in this PR, but I dislike the use of the word "translator"/"translatable" etc that gets used in Yomitan. I think we could rename it something like "lookup"/"lookupable", maybe.

2. Also maybe more related to this PR, I'm not sure whether "-able" is actually the right suffix at all, as it is possible to look stuff up even if it doesn't have the target language in it or not (like TKG and other Japanese words written in the English alphabet). I think the concept is closer to "lookup-worthy" -- i.e., a somewhat subjective threshold whether it's worth doing the lookup or not.

[toasted-nutbread]

1. The first is kind of unrelated to the change in this PR, but I dislike the use of the word "translator"/"translatable" etc that gets used in Yomitan. I think we could rename it something like "lookup"/"lookupable", maybe.

Agree, it's not really doing a true translation. Part of the reason why Translator has its name is because legacy, but I agree that it's a misnomer.

2. Also maybe more related to this PR, I'm not sure whether "-**able**" is actually the right suffix at all, as it is _possible_ to look stuff up even if it doesn't have the target language in it or not (like TKG and other Japanese words written in the English alphabet). I think the concept is closer to "lookup-**worthy**" -- i.e., a somewhat subjective threshold whether it's worth doing the lookup or not.

Updated this to isTextLookupWorthy.