Studio: Add chat context

[kozer]

Proposed Changes

This PR handles adding extra chat context to the API request.
Fixes: https://github.com/Automattic/dotcom-forge/issues/7601

Testing Instructions

1. Apply D152354-code
2. Run the above Studio pr locally.
3. Make sure you have at least 1 site.
4. Make questions related to your site:

eg: what is my wordpress version? What is my php version? What are my themes?

5. Ensure that you get the correct response like below:

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[kozer]

NOTE: We ll need to change things if #213 is merged first.

[fluiddot]

I tested different prompts and worked great, awesome work @kozer 🏅 !

Additionally, I shared some comments but I think none should block the PR.

For reference, with the prompt Share the context of the site we can easily see the values passed for the current site:

[kozer]

@fluiddot , I did all the changes you requested. Can you please check again? Thanks!

[sejas]

@kozer , the happy path works great! I've been updating the php version and installing plugins. It works great. Here is an screenshot.

I have a concern about running wp-cli commands multiple times when the site or focus changes. I found that changing the site in the left sidebar has a performance issue and freezes the app, even in the overview tab. Is possible to fix it?

Hhodxe.mp4

17McGF.mp4

[fluiddot]

@fluiddot , I did all the changes you requested. Can you please check again? Thanks!

They look great, thanks 🙇 !

[fluiddot]

I have a concern about running wp-cli commands multiple times when the site or focus changes. I found that changing the site in the left sidebar has a performance issue and freezes the app, even in the overview tab. Is possible to fix it?

Oh, I've just noticed this issue when selecting different sites, thanks for spotting it @sejas. Sorry to overlook it when testing it, as it severely impacts the performance of basic actions like selecting sites 😞 .

I think the main problem comes from the fact that the initial load is only marked as complete when all promises are finished (reference). A potential workaround could be to mark it as complete right before invoking the promises to avoid executing the wp-cli commands multiple times. In case they fail, we could mark the initial load as empty to let the app try again later on.

Another enhancement would be to debounce the run to avoid invoking multiple times the wp-cli commands when selecting different sites quickly.