[PROPOSAL] provide spring AutoConfiguration support

[Maglore]

What/Why

What are you proposing?

Provide an AutoConfiguration for spring opensearch library like it is done for elastisearch

What problems are you trying to solve?

Currently the RestClient has to be build from every user and every user has to define its own properties.
This can unified and simplified with this configuration.

What is the developer experience going to be?

This should ease the start of other spring developers with this library.

Are there any security considerations?

No, even if done correctly some basic security configurations can be made here.

[dblock]

Good idea. Care to contribute @Maglore?

[reta]

I have opened spring-projects/spring-boot#33011 so we could get Elasticsearch auto configuration out of our way (related issue is spring-projects/spring-boot#33010)

[dlvenable]

Perhaps we should split this project into two modules:

1. The core module. It would depend only on Spring Data.
2. A Spring Boot starter with the auto configuration.

[reta]

+1 to have dedicated starter module, we also have an issue which I was trying to address in Spring Boot but it was rejected: we sadly have to find a way to exclude (may be using AutoConfigurationExcludeFilter or alike) the ElasticsearchDataAutoConfiguration since it needs the Elasticsearch Java Client no matter what.

[reta]

@Maglore if you are not working on it, I would like to pick it up so we should be ready for mid-November Spring / Spring Boot / Spring Data Elasticsearch releases, thanks!

[Maglore]

@reta, yes sry i have currently no time to work on it, sry for the late answer