Fix glossary term matching for Japanese docs

[josh-wong]

Description

This PR fixes the component GlossaryInjector, which is used for showing terms in the glossary across pages. The problem was that many glossary terms were not showing on Japanese pages because those terms weren't detected with/without plurals, which was specific to only English terms. The problem occurred after introducing support for glossary terms in plural form in #834.

To fix this issue, I've refactored glossary term detection to better handle Japanese language pages by avoiding word boundaries and pluralization logic that are not applicable. This ensures accurate glossary injection for both English and Japanese documentation.

Related issues and/or PRs

• Problem introduced in Refine glossary tooltip feature (support capitalized terms and plural forms, remove tooltip from terms in backticks) #834.

Changes made

• Introduced isJapaneseSite flag: Added a flag to detect if the current site is Japanese (/ja-jp/) and reused this flag across multiple sections for cleaner and consistent logic. ([1], [2])
• Regex pattern adjustments: Modified the regex pattern generation to avoid word boundaries for Japanese terms, ensuring compatibility with Japanese characters. (src/components/GlossaryInjector.tsxL96-R112)
• Base term matching logic: Adjusted the logic for finding base terms in the glossary. Japanese terms now require an exact match, while English terms still support singular and plural forms. (src/components/GlossaryInjector.tsxL110-R136)
• Pluralization logic: Restricted pluralization handling to English terms, ensuring that Japanese terms are processed correctly without unnecessary modifications. (src/components/GlossaryInjector.tsxL141-R163)

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have updated the side navigation as necessary.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A