test(events): cover mount fetch, contractId propagation and polling lifecycle for ContractEventFeed (Closes #558)

[BernardOnuh]

Closes #558.

What

Adds the two acceptance-criteria behaviors that ContractEventFeed.test.tsx was still missing. The file already covered list rendering, empty state, error state, initial-load skeleton, and pausing polling — so this PR fills the remaining gaps:

• fetches events on mount with the contractId and the default limit — asserts the first call lands on mount with (CONTRACT_ID, 10, undefined) and fires exactly once, locking in the initial-fetch contract from the issue's Problem statement.
• restarts polling when the Live/Paused toggle is turned back on — pauses (no new calls after advancing well past the interval), then resumes and verifies one new call fires per poll interval. The issue explicitly calls out "Live toggle stops and restarts polling"; only the stop half had tests.

Verification

• npx vitest run src/components/ContractEventFeed.test.tsx → 35/38 pass; the 3 failures are the pre-existing JSON export (test: BalanceList search filter and sort modes, TransactionHistory status filter API params, ContractEventFeed export and topic copy #352) tests, which fail identically on clean main (verified via git stash) and are unrelated to this change.
• npx eslint src/components/ContractEventFeed.test.tsx → clean.

The polling tests drive vi.useFakeTimers() + vi.advanceTimersByTime() against the component's setInterval(load, pollInterval) wiring.

[drips-wave]

@BernardOnuh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits