Expand Troubleshooting Documentation page

[pratik-mahalle]

Describe the bug

The current troubleshooting section only contains guidance on changing log levels. Given the complexity of Microcks features (dispatchers, async protocols, Keycloak integration, etc.), users would benefit from expanded troubleshooting content.

Proposed Solution
Expand the troubleshooting (_index.md) page with additional sections covering common issues and their solutions.

Attach any resources that can help us understand the issue.

You can Expand the existing page with additional sections covering common issues:

• Import Issues - artifact validation errors, encoding problems, "no service found"
• Mock Not Responding - 404 errors, wrong responses, dispatcher debugging
• Authentication/Keycloak Issues - 401 errors, token problems, CORS
• Async API / Kafka Issues - broker connectivity, Schema Registry, SSL config
• Performance Issues - slow responses, memory usage, startup time
• Each section will use collapsible
  Details

  elements (already used in the file) for clean organization.

Breaking change? No - this is purely additive documentation content.

[lbroudoux]

Agreed with the benefits and the approach. Let's do it by iteration: each section at a time. So that we can discuss the level of granularity of the information we want to place here. To me, IMHO, a troubleshooting section is almost here, listing things to check with pointers to existing documentation - I shouldn't contain too much content on its own.