Match AI GraphQL subscription responses to the right feature

We now have the clientSubscriptionId available to match the requests and responses on the Frontend. Next steps are:

• Add clientSubscriptionId
• Document the clientSubscriptionId and how to use it
• Use a global clientSubscriptionId for chat to sync all messages
• Align all existing features to use the clientSubscriptionId
• Remove resourceId from the aiCompletionResponse

Why do we need this?

Right now, all of our AI features have a bug where they show the response from other AI features. e.g. when you want to Explain a Vulnerability, and have the chat open, the chat shows the response from the explained vulnerability. By using a unique clientSubscriptionId per request (or at least per feature per page), we no longer run into this issue.