Handle malformed responses in Vulnerability resolution
What does this MR do and why?
When testing Vulnerability Resolution, I noticed incidents when LLM responded with wrong xml tags. This results with undefined error shown to user.
I propose handling this situations, showing information to user with a request to try again.
To try again, we need to clear cache.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
To set up vulnerability, please see validation steps here: !160098 (merged)
Unfortunately, it's hard to reproduce it since responses from LLM are not deterministic. Specs are showing the situation I saw once in the real life.