sb3: bump elasticseach container to v8.5.0

[mshima]

---

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]

@mshima This PR seems to have a lot less failures than the current Spring Boot 3 branch. Should we merge it?

[mshima]

@mraible actually, this is due to diff logic applied to the workflows. If there is no change to the generated source, the test is skipped.
It doesn’t fix anything, every elasticsearch project broke, while others didn’t change.

[mraible]

So Elasticsearch v7.17.4 works fine with Spring Boot 3, but v8.5.0 does not? Maybe @xeraa can help.

[mshima]

@mraible no it's just the docker health check that is not working.

generator-jhipster/generators/docker/templates/src/main/docker/elasticsearch.yml.ejs

Lines 35 to 37 in 75898e4

	test: ['CMD', 'curl', '-f', 'http://localhost:9200/_cluster/health?wait_for_status=green&timeout=10s']
	interval: 5s
	timeout: 10s

[xeraa]

So, since 8.0 security is enabled by default. That means HTTPS only and a random password for the elastic user. Which is generally good, but would make your setup quite a bit more complex. And the health check is the first thing failing — not entirely surprising 😅

You could disable security for this scenario (please, don't do this in general)? I think this should get you sorted:

environment:
  - xpack.security.enabled=false