Enables Copilot to send cookies when calling Chainlit server

[mattgartman]

Enables the Copilot functionality to send cookies with requests to the Chainlit server. This allows support for cookie based sticky sessions.

Since withCredentials does not work when a server sets a wildcard CORS origin policy, this update exposes an operational parameter for users needing cookies to be sent with requests.

This PR addresses #1279.

[dokterbob]

@dosu Could you please add appropriate labels to this PR?

[dokterbob]

Sorry it took us a while to get back to this.

I just found this related PR, it seems it's covering the same scope -- it just misses a minimal update to useChatSession. #1497

Perhaps there's the opportunity for collaboration to solve these issues in one go? @nethi @mattgartman @ShubhamMaddhashiya-bidgely

[ShubhamMaddhashiya-bidgely]

@dokterbob In this PR, along with changes in libs/react-client/src/useChatSession.ts, there are other changes in copilot-related files to pass the send cookies bool from top to socket client.

We would need similar changes for chainlit app (webapp) side right?

Perhaps there's the opportunity for collaboration to solve these issues in one go?

are you proposing we combine these two PRs?

[dokterbob]

@dokterbob In this PR, along with changes in libs/react-client/src/useChatSession.ts, there are other changes in copilot-related files to pass the send cookies bool from top to socket client.

We would need similar changes for chainlit app (webapp) side right?

Perhaps there's the opportunity for collaboration to solve these issues in one go?

are you proposing we combine these two PRs?

Yes and/or help review each other's work.

[ShubhamMaddhashiya-bidgely]

Hey @mattgartman, what do you think about introducing a generic configuration object that can be passed to the SocketIO client instead of adding each parameter individually? Alternatively, we could allow passing a pre-configured client instance directly from upstream methods.