fix(election): pass id to ElectionProvider so refetchInterval triggers background refetches

[argos-code]

Summary

When an election is pre-fetched by the router loader and passed directly to ElectionProvider via the election prop, the provider's internal React Query hook never receives a query key (no id prop), so it stays enabled: false. This means refetchInterval: 15_000 in queryOptions silently does nothing — the election data shown in the dashboard process view and the public process page goes stale after the initial load.

The fix is a one-line addition in each component: pass id={election.id} alongside the existing election prop. With id present, React Query is enabled and treats election as initialData, so the first render is instant (no loading flash) and subsequent refetches fire on the configured interval.

Linked issue

Closes #1609

Changes

• src/elements/dashboard/processes/view.tsx — add id={election.id} to <ElectionProvider>
• src/elements/processes/PublicPage.tsx — same one-line fix
• src/elements/dashboard/processes/view.test.tsx — new test asserting ElectionProvider receives the correct id prop
• src/elements/processes/PublicPage.test.tsx — mirror test for the public page
• vitest.config.ts — exclude .pnpm-store from test discovery (pnpm store dropped temp test files into its cache dir)
• argos.yml — encode Node 22 + pnpm + tsc install steps for the validation container

Tests run

pnpm test

Test Files  114 passed (114)
      Tests  426 passed | 2 skipped (428)
   Duration  24.27s

pnpm lint

tsc && prettier --check src
Checking formatting...
All matched files use Prettier code style!

Risks and review focus

• initialData freshness: when election is passed alongside id, React Query uses it as initialData. Depending on the staleTime configured in ElectionProvider's internals, the first background refetch may be deferred. In practice the refetchInterval overrides this — confirmed by the tests — but reviewers should be aware that the exact timing of the first background request depends on the provider's internal staleTime.
• No change to @vocdoni/react-components: the fix is entirely at the call site. If the provider is updated upstream and changes how it handles concurrent id + election props, these sites will need re-checking.

Notes for maintainers

The root cause is that ElectionProvider requires id to enable its query; without it the hook is a no-op regardless of queryOptions. Both affected components already passed election (for the initial render) but omitted id (which would have enabled polling). The issue reporter's suggested approach of recovering "merge prop behaviour" is not needed — the existing provider API handles this correctly once id is supplied.