Migrate CassandraChatMemory to CassandraChatMemoryRepository

[markpollack]

This would allow us to have a more robust implementation than we currently have based on the ChatMemory.get(conversationId, lastn) interface that is currently deprecated.

This has been done for Jdbc in the PR - as a basis for comparison.

#2890

[linarkou]

As for now, cassandraChatMemory stores data in table with 4 columns like that:

create table ai_chat_memory (
    session_id        text,
    message_timestamp timestamp,
    assistant         text,
    user              text,
    primary key (session_id, message_timestamp)
)
    with clustering order by (message_timestamp desc);

Maybe we should change table structure similar to JdbcChatMemory?

create table ai_chat_memory (
    session_id        text,
    message_timestamp timestamp,
    type              text,
    content           text,
    primary key (session_id, message_timestamp)
)
    with clustering order by (message_timestamp desc);

It'll give us an ability to store tool/system messages, not only user/assistant.

What do you think @markpollack @michaelsembwever ?

[michaelsembwever]

Maybe we should change table structure similar to JdbcChatMemory?

Then the table would need a primary key like

primary key (session_id, message_timestamp, type)

Which can be done, and I have nothing against such an approach.

[linarkou]

Can't session_id+message_timestamp be a primary key? As far as I remember you set unique timestamp.

On other hand, there is #2902 with request on message id field, so we can introduce it here.

[michaelsembwever]

@linarkou , let's create a separate issue for your suggestion, as there's a time-constraint to get this issue fixed.

[michaelsembwever]

@markpollack draft PR @ #3036
eta to finish it tomorrow.

[michaelsembwever]

#3036 is ready for review now.