refactor(i18n): standardize localization key references across components

[aasimsyed]

Issue: #1100

• Migrate all inline i18n keys to use i18nMap object for type-safe references
• Add consistent 'i18n.' namespace prefix to translation keys in:
  • EmptyState component buttons
  • CardGetInvolvedOrganization links
  • CardSearchResult aria labels
  • MediaMap control tooltips
  • ModalEditFaqEntry text checks
  • Group/resource creation pages
  • Sidebar navigation labels
• Update HTML title attributes to use translated strings via i18nMap
• Import i18nMap in files where missing (MediaMap, groupSubPages)
• Fix key consistency in discussion input component

Contributor checklist

• This pull request is on a separate branch and not the main branch
• [] I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

Related issue

• #ISSUE_NUMBER

[netlify]

✅ Deploy Preview for activist-org ready!

Name	Link
🔨 Latest commit	86969f8
🔍 Latest deploy log	https://app.netlify.com/sites/activist-org/deploys/67a3dda8d59378000837e38f
😎 Deploy Preview	https://deploy-preview-1118--activist-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Thank you for the pull request! ❤️

The activist team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider attending our bi-weekly Saturday developer syncs! It'd be great to meet you 😊

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[aasimsyed]

@andrewtavis I didn't know how to fix this one from /frontend/components/combobox/ComboboxTopics.vue (lines 117-129): (if it even needed fixing)

  if (inputFocussed.value) {
    return "";
  } else {
    return selectedTopic.value.id == 1
      ? "Filter by topic"
      : selectedTopic.value.name;
  }
}

const displayValueHandler = () => {
  return i18n.t(displayValue());
};```

[andrewtavis]

I'll get the formatting check in the review here, @aasimsyed :) No stress 😊

[andrewtavis]

Bit of Vue learning here, @aasimsyed: What we do here is preppend label with :, which is short for v-bind:label (see v-bind docs on W3 Schools). This allows us to pass a variable inside of a string. I'll fix these quickly 😊

[andrewtavis]

And in the comment above, good catch! We should include that string in the i18n values :) I'll add that in as well :)

[andrewtavis]

Nice, @aasimsyed! This is great 😊 I'm realizing that there are a few more that can be found in cases that are not the search methods that I defined in the issue, so let me detail those and then you can take those down as well :)

Wonderful to work with you again!