Update patch plugin versions in gemfile lock (#18777)

Update patch plugin versions in gemfile lock (#18778)

Update patch plugin versions in gemfile lock (#18779)

Revert "Update bundled JDK to 21.0.10 build 7 (#18648)" (#18663)

This reverts commit 82a51fb.

Revert "Update bundled JDK to 21.0.10 build 7 (#18650)" (#18664)

This reverts commit 86458b5.

Update patch plugin versions in gemfile lock (#18618)

Change kafka integration dependency to 11.x (#18553)

The original dependency bump changed the kafka dependency to 12.x which
introduces a breaking change. This reverts the change back to 11.x

Update patch plugin versions in gemfile lock (#18546)

Co-authored-by: logstashmachine <43502315+logstashmachine@users.noreply.github.com>

Update patch plugin versions in gemfile lock (#18547)

Co-authored-by: logstashmachine <43502315+logstashmachine@users.noreply.github.com>

[8.19] (backport #18423) Rewrite Env2yaml in java instead of Go (#18456)

* Rewrite Env2yaml in java instead of Go (#18423)

* WIP: Rewrite Env2yaml in java instead of Go

Managing a Go toolchain for persisting ENV vars in logstash container artifacts
has become cumbersome. We already manage a java runtime so this commit presents
a path forward to use that instead of Go. The Go binary is faster than java (in
my testing Go would complete in around less than 200ms while java takes over
300ms). Given the container startup time is on the order of magnitute of seconds
this change should be inperceptable to consumers. The benefit from consolidating
in Java is worth the slightly lower performance.

* Use TreeMap in java to try to replicate lexicographical order

* Explicit imports and TreeMap everywher

* Go removals and ironbank workflow update

* More non-code removals

* Update based on codereview

Use snakeyaml-engine and some java flags for faster execution

* Build env2yaml in stage

Build env2yaml in a separate build stage for container artifacts. Include
its dependencies and manage separately from logstash. Continue to use the
java runtime in the final container to run the program, but manage the classpath
separately. Note this did not use gradle for dependency management because installing
that as a depdendcy was not worth it compared with downloading a jar directly.

* Use gradle to manage snakeyaml-engine dependency

Use gradle (and a dedicated gradle base image) for building env2yaml

* Refactor to build env2yaml with gradle rather than in docker build

Dont rely on compiling at docker build time, rather do it when logstash
compilation is done.

* Dont try to use snakeyaml from jruby

The complexity around trying to copy over the jar shipped with jruby is not worth
how easy it is to just manage it with gradle. This helps with keeping env2yaml contained.

* Add license for snakeyaml-engine

Licence from https://bitbucket.org/snakeyaml/snakeyaml-engine/src/master/LICENSE.txt

* Cleanup and bugfix

* Stop skipping empty env vars

I mistakenly thought I had observed this behavior in the go version.

* Remove quotes from interpolated values

Even though we set `.setDefaultScalarStyle(ScalarStyle.PLAIN)` snakeyaml-engine
ends up quoting `${}` values. This commit removes them as this was not the behavior
with the go version.

(cherry picked from commit b15c6c5)

# Conflicts:
#	docker/Makefile
#	docker/data/logstash/env2yaml/env2yaml.go
#	docker/templates/Dockerfile.erb
#	docker/templates/IronbankDockerfile.erb
#	rakelib/artifacts.rake
#	settings.gradle

* fix merge conflicts

* Actually delete unused go source for env2yaml

---------

Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>