fix: Exclude version upgrade fixes in "no fixable issues" test

The test "should handle workflow with no fixable issues" was failing
because the new version upgrade feature (added in this PR) detected
that the test's webhook node (version 2) was outdated compared to
the database version (2.1), and suggested a version upgrade fix.

Solution: Explicitly exclude 'typeversion-upgrade' and 'version-migration'
fix types from this test using the fixTypes parameter. This preserves
the test's original intent of verifying the "no fixes available" code path.

This follows the pattern used in other tests in the same file that
use fixTypes to limit the scope of autofix operations.

Fixes CI integration test failure in autofix-workflow.test.ts

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Conceived by Romuald Członkowski - https://www.aiadvisors.pl/en

tests/integration/n8n-api/workflows/autofix-workflow.test.ts

@@ -623,7 +623,9 @@ describe('Integration: handleAutofixWorkflow', () => {
       const response = await handleAutofixWorkflow(
         {
           id: created.id,
-          applyFixes: false
+          applyFixes: false,
+          // Exclude version upgrade fixes to test "no fixes" scenario
+          fixTypes: ['expression-format', 'typeversion-correction', 'error-output-config', 'node-type-correction', 'webhook-missing-path']
         },
         repository,
         mcpContext