refactor: V3 swap integration test with persistence

[johngrantuk]

Refactors V3 swap integration tests to use persisted test data for faster runs.

Changes:

• New test suite (test/entities/swaps/v3/swap.integration.test.ts):
  Integration tests for V3 swaps covering:
• Native input/output handling
• Permit2 direct approval flows
• Both GivenIn and GivenOut swap kinds
• Conditional fork setup: only starts forks when saved test data is missing
• Test data persistence: saves query outputs and call data to JSON for reuse

Test data file (test/entities/swaps/v3/swapTestData.json):

• Stores serialized query outputs and call data
• Enables tests to run without fork setup when data exists

Benefits

• Faster test execution: skips fork setup and query calls when saved data exists
• Deterministic comparisons: compares serialized call data against saved values
• Maintains full integration coverage: still runs full assertions when data is missing
• Better test isolation: uses snapshots for consistent test state

[johngrantuk]

I think this might be where the current issues come from - at least locally it seems like the jobId isn't unique for each test. So we have multiple tests running in parallel reseting/altering state on the same fork which causes issues with nonces, etc. I think the same might also be happening in a single test file where different tests run in parallel and reset to snapshot. Using sequential should stop that.