For nested pluralization keys, i18n-ally usage report inaccurately indicates unused/not found keys

[mkevinosullivan]

Describe the bug
When using nested pluralization keys, e.g., with a locale file like

{
  "levelOne" : {
    "levelTwo": {
      "one": "{{count}} level",
      "other": "{{count}} levels"
    },
  }
}

and a code snippet of

const content = t("levelOne.levelTwo", { count: count})

the usage report indicates that the levelOne.levelTwo key is missing, and that keys levelOne.levelTwo.one and levelOne.levelTwo.other are not in use.

When using nested pluralization keys, the expectation would be that levelOne.levelTwo is not reported as missing and that keys levelOne.levelTwo.one and levelOne.levelTwo.other are considered in use IF levelOne.levelTwo is used in the source file.

Extension Version
i18n Ally (v2.9.1)

Framework/i18n package you are using
react-i18next (will also apply to yet-to-be-released i18next-shopify framework, based on react-i18next)

To Reproduce
Steps to reproduce the behavior:

1. Go to examples/by-framework/react-i18next in the i18n-ally repo
2. Update the public/locales/en/translation.json file to be

{
  "title": "hello",
  "description": {
    "part1": "To get started, edit <1>src/App.js</1> and save to reload.",
    "part2": "Switch language between english and german using buttons above."
  },
  "titlew": "ok",
  "foo": {
    "bar": "foobar"
  },
  "messages": {
    "one": "You have {count} message.",
    "other": "You have {count} messages."
  }
}

3. Open the src/App.jsx file and add the following component after MyComponent:

function MyMessagesComponent() {
  return <p>{t('translation:messages', { count: 1 })}</p>
}

4. Refresh the usage report
5. See error
   

Device Information

• OS: Mac OS
• Version: Ventura 13.4
• VS Code Version: 1.79.2

Extension Log
Go to View -> Output -> i18n Ally, and paste the content below.

🈶 Activated, v2.9.1

――――――

💼 Workspace root changed to "/Users/XXXXXXXXXX/src/github.com/lokalise/i18n-ally/examples/by-frameworks/react-i18next"
🌞 Enabled
🧩 Enabled frameworks: React I18next, General
🧬 Enabled parsers: json, yaml, json5

📈 Telemetry id: 135ba03d-a31d-47be-bb68-22da5751c001
[telemetry] enabled: undefined
[telemetry] user: {"version":"2.9.1","feature_auto_detection":true,"feature_annotation_in_place":true,"feature_annotations":true,"feature_disable_path_parsing":false,"feature_extract_auto_detect":false,"feature_keep_fulfilled":false,"feature_prefer_editor":false,"feature_review_enabled":true,"feature_has_path_matcher":true,"feature_has_custom_framework":false}
🚀 Initializing loader "/Users/XXXXXXXXXX/src/github.com/lokalise/i18n-ally/examples/by-frameworks/react-i18next"
📂 Directory structure: dir
🗃 Custom Path Matcher: {locale}/{namespaces}.json
🗃 Path Matcher Regex: /^(?<locale>[\w-_]+)\/(?<namespace>.+)\.json$/

📂 Loading locales under /Users/XXXXXXXXXX/src/github.com/lokalise/i18n-ally/examples/by-frameworks/react-i18next/public/locales
	📑 Loading (de) de/translation.json [1686234424753.6492]
	📑 Loading (en) en/translation.json [1687378585111.2266]
	📑 Loading (de) de/pages/home.json [1686234424752.8743]
	📑 Loading (en) en/pages/home.json [1686234424753.829]

👀 Watching change on /Users/XXXXXXXXXX/src/github.com/lokalise/i18n-ally/examples/by-frameworks/react-i18next/public/locales
✅ Loading finished