See gh-25451

See gh-25450

See gh-25449

Closes gh-25450

Closes gh-25449

Previously, actuator endpoints were registered with Jersey upon
injection of the ResourceConfig bean into a registrar class rather than
using a ResourceConfigCustomizer. This was done to fix a problem
when running the Actuator on a separate port where the main application
context's customizers were also applied to the management context,
breaking the singleton contract for those resources. This approach
meant that the registration could be performed at any point after the
ResourceConfig had been created. When Jersey's configured as a Filter
this resulted in the registration failing as the attempt was being made
after the Filter lifecyle callbacks which make the ResourceConfig
immutable.

This commit reworks the endpoint registration to be performed using a
ManagementContextResourceConfigCustomizer, a resource config customizer
that's only applied to the ResourceConfig that's used by the Actuator.
When there's a separate management context, this ResourceConfig is
created by the Actuator's auto-configuration and the management context
resource config customizers are applied to it during its creation. The
main application's customizers are not applied. When the actuator is
using the same context as the main application, this ResourceConfig is
created by the main application. In this case a
ResourceConfigCustomizer is defined that delegates to all
ManagementContextResourceConfigCustomizers, allowing them to register
the actuator endpoints with the main ResourceConfig.

Fixes gh-25262

Closes gh-25448

Closes gh-25447

* gh-25446:
  Split DeploymentIntegrationTests by container
  Rename DeploymentIntegrationTests

Closes gh-25446

Prior to this commit, every test started a new testcontainer. By splitting the
tests apart we can make use of static containers that are only instantiated once
per application (TomEE, Wildfly etc.)

See gh-25446

See gh-25446

This commit updates LoggingApplicationListener to register the logging
shutdown hook by default.

The hook is detrimental in a war deployment as it may pin parts of an
application in memory after it has been undeployed. For this reason,
the hook is still disabled by default in war deployments. This is
achieved by setting an attribute on the servlet context in
SpringBootServletInitializer that is then consumed via the Environment
by LoggingApplicationListener.

Closes gh-25046

* gh-25445:
  Ignore empty prefixes in new PrefixedConfigurationPropertySource

Closes gh-25445

See gh-25445

We configure the `SystemEnvironmentPropertySource` as a `Prefixed` property
source. When adapting this to a `ConfigurationPropertySource, a
`PrefixedConfigurationPropertySource` will be created for it.
A `PrefixedConfigurationPropertySource` will resolve property
such as `foo.bar` to `my.foo.bar` for a prefix of `my`.

Closes gh-3450

Closes gh-25441

Closes gh-25440

* gh-25434:
  Remove spring-boot-smoke-test-jta-jndi

Closes gh-25434

See gh-25434

Closes gh-25438

Closes gh-25437

* gh-25409:
  Enable stricter validation for Gradle plugin

Closes gh-25409

See gh-25409

Closes gh-25432

* pr/25411:
  Fix grammatical error in documentation

Closes gh-25411

See gh-25411

Closes gh-25431

Closes gh-25430

* gh-25412:
  Update Testcontainers image versions

Closes gh-25412

See gh-25412

Closes gh-25429

Closes gh-25428

Closes gh-25427

Closes gh-25426

Closes gh-25425

Closes gh-25424

Closes gh-25423

Closes gh-25422

Closes gh-25421