[MCP] Include API Version in MCP Configuration Import/Export

[onbuyuka]

Fix: Include API Version in MCP Configuration Import/Export

Problem

When exporting and importing MCP configurations, the API Version field on configuration tools was not included in the JSON payload. This meant that after a round-trip (export → import), all tools would lose their API version, silently defaulting to an empty value.

Changes

MCPConfigImplementation.Codeunit.al

• Export: Added apiVersion property to each tool object in the exported JSON.
• Import: Added parsing of the apiVersion property when importing tools, populating API Version on the MCP Configuration Tool record.

MCPConfigTest.Codeunit.al

• CreateMCPConfigTool now sets API Version := 'v2.0' to ensure export produces a realistic payload.
• TestImportConfiguration now asserts that the imported tool retains the correct API version after round-trip.

Testing

• Existing TestExportConfiguration and TestImportConfiguration tests now cover the apiVersion field end-to-end.

Fixes AB#621816

[github-actions]

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.

---

🔄 How to trigger a new status check:

1. 📤 Push a new commit to the PR branch, or
2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.