Add factory method to LettuceConnectionFactory to create RedisConfiguration from RedisURI

[onobc]

Fixes gh-2116

@markpollack I know this still needs formatting and tests written but I wanted to push the proposal that I have so far to make sure this is what you had in mind. I will follow on w/ the formatting and tests once you confirm (or not).

Thanks

• 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).

[mp911de]

Thanks for your pull request. I left a few comments. You can find the formatter settings at https://github.com/spring-projects/spring-data-build/tree/main/etc/ide

[onobc]

Adding tests now.

[onobc]

@mp911de well I just realized that "Mark Pollack" whom I mentioned in original description != "Mark Paluch" 🤦.

I am leaving WIP as I want to consume these changes locally to verify it is what we want for spring-projects/spring-boot#21920 so as to avoid any churn in case this proposal needs to be tweaked slightly. I should be able to do that sometime w/in next 24 hrs.

Of course, if you would rather merge it before I do that - that is fine too.

[onobc]

A few things to note about this test:

1. I opted to test the functionality at LettuceConnectionFactory.createRedisConfiguration rather than directly on the LettuceConverters.redisUriTo<T>Configuration as the tests would have been almost identical. The coverage is the same doing it this way. The assumption is that the LC methods are an internal impl of this API. Also, because the LC methods are static, just unit testing the routing in LCF to LC (that is all that the LCF really is doing) would have been problematic to mock.

2. I broke it out into its own specific LCF unit test as the other one is getting pretty big.

3. I leveraged @Nested to group the "flavor" of RedisConfiguration under test.

[mp911de]

I'd suggest introducing proper equals/hashCode methods, that's something we can do during the merge.

[onobc]

Yeh good call. I was wrapped up in Lettuce specific-land that I did not realize the config objects were not lettuce constructs - they are clearly spring data redis and I could have added EHC rather than the AssertJ field by field config approach.

[mp911de]

This looks pretty decent. Let me polish up the last bits here and take care of the merge.

[mp911de]

Thank you for your contribution. That's merged, polished, and backported now.