Add integration module with quarkus-websockets-next

[geoand]

This module allows for automatic use of memoryId when no object is specified

TODO: add tests, fix for native image and add documentation

[jmartisk]

Are you also going to update the samples that use websockets?

[geoand]

I will after this, yes

[jmartisk]

LGTM! Tried migrating my own project to it and it worked.

[jmartisk]

Hm, one inconvenience that I now noticed is that by making the AI service session-scoped, I can no longer call it from a REST endpoint. I don't quite understand why we need to make it session-scoped? Isn't the service in itself stateless and only controlled by what the memory contains?

[geoand]

I don't quite understand why we need to make it session-scoped?

By making it @SessionsScoped we are able to automatically remove all memory when the websocket session closes.

Isn't the service in itself stateless and only controlled by what the memory contains?

It is, but it integrates with memory and can thus be used for automatic memory management.

I can no longer call it from a REST endpoint

I suggest using different AI services.