Add overloads for XAddOptions in StreamOperations

[jinkshower]

Closes #2915

After this change, the client can use XAddOptions as an additional parameter for opsForStream.add()

TO-BE

XAddOptions options = XAddOptions.maxlen(1).approximateTrimming(false);
redisTemplate.opsForStream.add("myStream", Map.of("key", "value), options);

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[jinkshower]

please review this pr and if this needs some changes, I will be happy to amend it!

[jinkshower]

the reason why I wrote somewhat verbose method in here is

unlike JedisStreamCommands or LettuceStreamCommands
which both have a method accepting (MapRecord<byte[], byte[], byte[]> record, XAddOptions options)

xAdd(Publisher commands) in LettuceReactiveStreamCommands
expects that Publisher already has variables of XAddOptions.
ex) maxlen, isApproxiateTrimming...

so I placed the decapsulation of XAddOptions here.

I thought of changing AddStreamRecord to have variable priavte final XAddOptions options
so that LettuceReactiveStreamCommands can delegate the decapsulation to other class
but I thought this exceeds the scope of this issue.

[jinkshower]

removed typo

[jinkshower]

I have a question regarding XAddOptions. While I was writing tests, I found out that

XAddOptions options = XAddOptions.maxlen(-1);
redisTemplate.opsForStream("myStream", Map.of("key", "value), options);

this executes and the result being maxlen option just not applied.

This is becasue in XAddOptions in RedisStreamCommands's hasMaxlen() method.

public boolean hasMaxlen() {
	return maxlen != null && maxlen > 0;
}

also same with AddStreamRecord in ReactiveStreamCommands.
this method just ignores minus value of maxlen.

As for redis, if user makes maxlen -1, An error occurs.

If we make hasMaxlen()

public boolean hasMaxlen() {
	return maxlen != null 
}

For Lettuce, Lettuce’s XAddArgs has LettuceAssert which asserts the value of maxlen.

For Jedis, Jedis’s XAddParams doesn’t have assertions. So redis server throws an exception.

IMO, it is better to alert user by throwing exception than the result just not applied because it is hard to find and also realise the problem.

The reason why I'm asking this question, instead incorporating into PR I created was I was not sure if this is intended.

If this needs to be fixed, I will make adjustment in this PR and push it again. If not, please let me know. Thank you.

[kkocel]

@jinkshower looks good to me :)

[jinkshower]

Hello, @christophstrobl. Could you please take some time to review this PR when you have a moment? I'm not entirely confident about some of the changes I've made, and your feedback would be incredibly valuable to me.

[christophstrobl]

@jinkshower thanks for the heads up.

[christophstrobl]

@jinkshower thank you for your contribution. Merged to main development line.
Regarding the maxlen please open a new issue.