refactor(web): use query key factories for safer and more consistent queries

[dgdavid]

Note

PR stil work in progress. Full description will be added once the PR is more polished.

Instead of writing query keys manually each time, this commit introduces
the use of query key factories. This helps prevent mistakes like typos
or mismatched keys, ensures consistency, and improves maintainability by
centralizing key definitions, making future changes easier.

This follows a recommended pattern from TanStack query blog:
https://tkdodo.eu/blog/effective-react-query-keys#use-query-key-factories

[coveralls]

coverage: 64.205% (-0.05%) from 64.253%
when pulling 9fb4792 on query-key-factories
into 9407017 on master.

[dgdavid]

Of course, would be more readable something like

const queryKeys = {
  all:       () => ["l10n"] as const,
  config:    () => ["l10n", "config"] as const,
  locales:   () => ["l10n", "locales"] as const,
  keymaps:   () => ["l10n", "keymaps"] as const,
  timezones: () => ["l10n", "timezones"] as const
}

or even,

const queryKeys = {
  all:       ["l10n"] as const,
  config:    ["l10n", "config"] as const,
  locales:   ["l10n", "locales"] as const,
  keymaps:   ["l10n", "keymaps"] as const,
  timezones: ["l10n", "timezones"] as const
}

But I'd go with the proposed approach of always using functions, to stay consistent with the rest of the query keys in the codebase. Some keys take parameters, and defining them all as functions keeps the API uniform and easier to work with.

About using composed keys ([...queryKeys.all(), "config"]) instead of hardcoding them (["l10n", "config"]), it also follows TanStack Query’s recommended practices. While it may slightly impact readability, it enables a layered composition strategy that simplifies future changes, especially when modifying top-level segments or adding new levels of nesting.

[dgdavid]

Above comment becomes more evident when looking at more complex query keys such as those in the software, network, or storage domains. There, the benefits of consistent structure and layered composition are much easier to appreciate.

[dgdavid]

Closing because base code will change a lot after ongoing changes in api-v2 branch.