Feat: Microcks-CLI v2 - IDE (Vs code) Integration and Local Dev Loop Enhancement

Nobody has claimed this yet.

### Reason/Context

- LFX Proposal

### Description

The Microcks CLI (microcks-cli, written in Go) is a key part of Microcks' CI/CD story - it lets developers trigger contract tests and import artifacts from the command line and in GitHub Actions. This project goes into the developer experience layer. Today, developers must navigate to the Microcks web UI in a browser to see test results, check mock status, and diagnose import errors. There is no IDE integration, no offline validation mode, and no way to get mock results inline with the code being tested. This project builds three focused improvements that bring Microcks into the editor and the local dev loop: a VS Code extension, a local dry-run mode powered by Testcontainers, and an updated GitHub Actions output format that annotates PRs with per-operation pass/fail results.

### Implementation ideas

_No response_

Start by reviewing the microcks-cli repository entry points for its current command-line, GitHub Actions, and test-result flows. The proposal describes three separate outcomes: a VS Code extension, a Testcontainers-powered local dry-run mode, and per-operation pass/fail annotations in GitHub Actions. Done means all three improvements are designed and implemented, but the issue does not identify files or tests to guide the work.

Written by the indexing model from the issue text.