test(cli): expand Open-Meteo e2e coverage

[yada]

Summary:

This PR expands the existing Open-Meteo CLI Vitest e2e scenario so it validates the MCP behavior exposed by the gateway, not only the import and exposition control-plane state.

Changes:

• switch the Open-Meteo scenario to reusable CLI, cleanup, and MCP helpers
• keep Open-Meteo scenario constants local to the scenario test
• split the scenario into named sequential Vitest steps for traceable e2e output
• validate imported service metadata and operation count
• validate active exposition backend configuration
• validate MCP initialize through the gateway
• validate MCP tools/list exposes get_v1_forecast
• call get_v1_forecast through MCP and assert the backend payload shape
• delete the imported service before logout and verify it cannot be fetched anymore
• verify logout removes the CLI config file from the isolated e2e home
• keep fallback cleanup in afterAll so partial failures still remove the imported service

Validation:

cd cli
npm run build
npm exec tsc -- --noEmit --target es2022 --module es2022 --moduleResolution node --strict --esModuleInterop --skipLibCheck e2e/global-setup.ts e2e/helpers/*.ts e2e/scenarios/*.ts
npm run test:e2e -- --reporter=verbose

Closes #218

[lbroudoux]

@copilot resolve the merge conflicts in this pull request

[lbroudoux]

Think it needs a rebase and some conflict resolution. Then remove the draft status.

[lbroudoux]

Ok but this it no longer a scenario as everything is now packed into a single test/step. Wouldn't it be easier for error tracking purpose to split into different steps/methods/tests?

[yada]

I checked the verbose Vitest output (run locally), and I agree with your point. The current test passes, but the report now only shows one scenario-level test:

imports Open-Meteo, exposes it, and serves MCP tools

Working on it to see how I can split tests into smaller steps for better traceability.

[yada]

Tested locally and here the output now ;)

Verbose e2e output now includes:

  ✓ ... > logs in and removes stale Open-Meteo service
  ✓ ... > imports Open-Meteo with backend endpoint
  ✓ ... > validates imported service metadata and operations
  ✓ ... > validates active exposition backend configuration
  ✓ ... > initializes MCP endpoint through gateway
  ✓ ... > lists Open-Meteo MCP tool
  ✓ ... > calls Open-Meteo forecast tool through MCP

  Test Files  1 passed (1)
  Tests       7 passed (7)

[lbroudoux]

LGTM