* pr/20192:
  Update copyright date
  Polish

Closes gh-20192

See gh-20192

See gh-20192

Closes gh-20106

Closes gh-20188

This commit also upgrades the Spring Boot version used by the scripts
to 2.2.4 which is why the explicit annotation is required.

Closes gh-20174

Closes gh-20183

Closes gh-20185

Closes gh-20186

* pr/20169:
  Polish "Document sanitized keys and uri sanitization behavior"
  Document sanitized keys and uri sanitization behavior

Closes gh-20169

See gh-20169

See gh-20169

* pr/19494:
  Polish "Add support for configuring Jetty's backing queue"
  Add support for configuring Jetty's backing queue

Closes gh-19494

See gh-19494

Closes gh-20183

See gh-19494

Closes gh-20135

Closes gh-20178

* pr/20168:
  Remove duplicate auto-configuration class

Closes gh-20168

See gh-20168

Closes gh-20117

Closes gh-19926

Closes gh-20045

Closes gh-20167

Closes gh-20166

Closes gh-20165

Closes gh-20164

Closes gh-20163

Closes gh-20162

Closes gh-20161

Closes gh-20092

Previously, dependency management for JNA was provided by
spring-boot-dependencies so it affected users' applications. It was
original added for Elasticsearch but is no longer needed for that
purpose. We use JNA in spring-boot-buildpack-platform which is used
by our Gradle and Maven plugins and should not affect an application's
use of JNA.

This commit moves management of JNA from spring-boot-dependencies into
spring-boot-parent. This means that users' applications will now be
free to use whatever version of JNA meets their needs while still
controlling the version used for image building via Gradle or Maven.

Closes gh-20156

Closes gh-20160

Closes gh-20159