fix: standardize i18n string references

[aasimsyed]

Issue: #1100

changes suggested by @andrewtavis

• Replace hardcoded i18n path strings with i18nMap references in components
• Update button labels and aria-labels to use i18nMap paths
• Remove unnecessary i18nMap imports where direct strings are preferred
• Maintain consistent i18n usage pattern across components

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	ba5793a
🔍 Latest deploy log	https://app.netlify.com/sites/activist-org/deploys/67a50aa1e3812f00071499d1
😎 Deploy Preview	https://deploy-preview-1119--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)

[andrewtavis]

Quick note that we'll need many of these component attributes to be v-bind: equivalents, where rather than label=... we'd have :label=... which then interprets the value in the string as a variable rather than a string, @aasimsyed :) In case you haven't installed the Vue plugin for VS Code, I'd do that as that'll then show you explicitly that it's reading in a variable instead of a string :) Sorry if you do have it installed, just making sure as there have been some changes 😊 You can check the recommended extensions in the dropdowns in the Environment Setup section of the readme :)

[andrewtavis]

And would be amazing if you could get the merge conflicts as well, but let me know if you need some help with those! :)

[andrewtavis]

I spoke too soon :) Thanks, @aasimsyed! 🚀

[aasimsyed]

Quick note that we'll need many of these component attributes to be v-bind: equivalents, where rather than label=... we'd have :label=... which then interprets the value in the string as a variable rather than a string, @aasimsyed :) In case you haven't installed the Vue plugin for VS Code, I'd do that as that'll then show you explicitly that it's reading in a variable instead of a string :) Sorry if you do have it installed, just making sure as there have been some changes 😊 You can check the recommended extensions in the dropdowns in the Environment Setup section of the readme :)

I'm not sure I understand what you mean here. You want those changes into this PR?

[andrewtavis]

Yes these changes would need to happen on each component attribute where we're trying to pass the result of the object as a variable. As it's written now in some cases then the string "i18nMap..." will be passed. With the colon at the start the string is interpreted as a variable. We still leave the quotes on either side so it looks the same on the right side, but the colon on the left changes what's interpreted.

Let me know if it's still confusing!

[aasimsyed]

Yes these changes would need to happen on each component attribute where we're trying to pass the result of the object as a variable. As it's written now in some cases then the string "i18nMap..." will be passed. With the colon at the start the string is interpreted as a variable. We still leave the quotes on either side so it looks the same on the right side, but the colon on the left changes what's interpreted.

Let me know if it's still confusing!

@andrewtavis please review. I think I did what you were asking for. Let me know if there are any other issues.

[andrewtavis]

A couple more instances needed to get changed, @aasimsyed, and with that I did a few updates for things that weren't quite working after some dependency updates.

Thanks so much for bringing this home, @aasimsyed! Really awesome to have this setup finalized 🚀

CC @OmarAI2003 that the i18nMap object is now in full use over here. One extra thing I realized for i18n-check is that we need to give the user the ability for the map file to be written with a license header. I made the changes to add the current way we do it over here into the project, and then we'll just need to add an option for what the license for the project is :)

[andrewtavis]

PS I ran the e2e tests and we're at the ~7 that are already failing, so we're good in those regards as well :)