Migrate to new Elasticsearch Java client for Spring Boot 3

[frascu]

Fixes #19934

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[mraible]

@frascu Can you please update your branch from spring-boot-3.0-m4?

[frascu]

Updated

[frascu]

My last commit is unrelated to ElasticSearch, but I fixed a compile error for @Type.
I found that this annotation has been removed and we can use @JdbcTypeCode.

It's described better here.

[frascu]

@mraible @DanielFran since the failed pipelines are not related to Elasticsearch migration, can this pull request be merged?

[mraible]

I'm OK with merging it. Is that OK with you, @mshima?

[mshima]

I prefer to merge after spring-boot rc1 release which is due in 3 days 20/10.
RC1 should bring the Problem feature, and maybe we can make some backend tests to pass before merging this PR.
Smaller PRs is much easier to review, the generated diff is quite hand.

@mraible unless if you plan to do some development that requires this PR.
So feel free to merge this PR and #20011 too if you want.

[mshima]

Closing/reopen to create a new merge point

[mshima]

Is this missing reactive implementation?
Or reactive kept the same?

Nevermind looks included.

[mraible]

I'm merging this PR so @frascu can collect a bug bounty for his work here.

[frascu]

Bounty claimed https://opencollective.com/generator-jhipster/expenses/102550 🙂

[frascu]

@DanielFran can you approve?

[DanielFran]

@frascu approved