chore: Update translation keys for consistency

[OmarBrbutovic]

What this PR does / why we need it:

Added script to check for translation keys in the codebase and ensure they are consistent with the i18n files.
Updated translation keys in various components and pages to follow a consistent naming convention.

Additional documentation e.g. usage docs, diagrams, reviewer notes, etc.:

---

Thanks for sending a pull request! If this is your first time, here are some tips for you:

1. You can take a look at our developer guide for an introduction on Edgehog development!
2. Make sure to read CONTRIBUTING.md and CODE_OF_CONDUCT.md
3. If the PR is unfinished or you're actively working on it, mark it as draft

When fixing existing issues, use github's syntax to link your pull request to it

fixes #<issue number>

We also have a syntax to signal dependencies to other open pull requests

depends on #<pr number>
depends on https://github.com/...

In case of stacked PRs, you may add the PR number in the last commit's title instead:

gitGraph
    commit id: "Current master"
    branch feat1
    checkout feat1
    commit id: "feat: add something"
    commit id: "feat: add something else (#100)"
    branch feat2
    checkout feat2
    commit id: "refactor: do something"
    commit id: "fix: solve issue"
    commit id: "feat: add a feature (#101)"
    branch feat3
    checkout feat3
    commit id: "feat: feat without pr number"

Loading

[ArnelaL]

/fast-forward