Introduce the sub-entry publish support

[Gsantomaggio]

it would be useful to have the sub-entry publish support.

see: https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle/#producer-sub-entry-size-configuration-entry

The internals:
https://github.com/rabbitmq/osiris/blob/HEAD/src/osiris_log.erl#L163-L263

[Gsantomaggio]

If want to know more detail about, please let me know.

[qweeze]

Thanks! I will look into it in the next few days

[Gsantomaggio]

In Java and Go have all the compressions type directly on the client:

NONE = byte(0)
GZIP   = byte(1)
SNAPPY = byte(2)
LZ4    = byte(3)
ZSTD   = byte(4)

In the .NET client, we decided to implement only GZIP and NONE then add the possibility to use external plugins to use:

SNAPPY = byte(2)
LZ4    = byte(3)
ZSTD   = byte(4)

I'd follow the same .NET policy

[Gsantomaggio]

To make it easy I would do as .NET like a send overload:

var subEntryMessages = List<Messages>();
for (var i = 1; i <= 500; i++)
{
    var message = new Message(Encoding.UTF8.GetBytes($"SubBatchMessage_{i}"));
    subEntryMessages.Add(message);
}

await producer.Send(1, subEntryMessages, CompressionType.Gzip);
messages.Clear();

So in python it would be:

publish(
        self,
        stream: str,
        message[] <--- array or list of messages
       compression_type

Note that for 1 publishing id you can have 1 or more messages.
publishing_id 1 ---> [] messages

[DanielePalaia]

Closing this one as already implemented in: #54