See gh-25457

Closes gh-25457

This commit harmonizes the fallback value that spring-boot:stop goal
should use if no information is available in the current context.

Closes gh-25472

* gh-25457:
  Speed up spring-boot-server-tests

Closes gh-25457

See gh-25457

Closes gh-25460

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

* 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

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

Closes gh-25434

See gh-25434

* gh-25409:
  Enable stricter validation for Gradle plugin

Closes gh-25409

See gh-25409

* gh-25412:
  Update Testcontainers image versions

Closes gh-25412

See gh-25412

Closes gh-25420

Closes gh-25419

Closes gh-25405

Closes gh-25392

* pr/25382:
  Update copyright year of changed file
  Fix wording error in build-info goal description

Closes gh-25382

See gh-25382

See gh-25382

* pr/25353:
  Polish HTTP client metrics documentation wording

Closes gh-25353

See gh-25353

Closes gh-25355

See gh-25355

See gh-25107

Closes gh-25283

Closes gh-25284

This commit reworks the CI pipeline to remove the use of Bintray for
publishing to Maven Central. In its place it adds a new
publishToCentral command to the release scripts. This command can be
used to publish a directory tree of artifacts to the Maven Central
gateway hosted by Sonatype.

Publishing consists of 4 steps:

1. Create the staging repository
2. Deploy artifacts to the repository
3. Close the repository
4. Release the repository

The command requires 3 arguments:

1. The type of release being performed
2. Location of a build info JSON file that describes the release
   that is to be deployed
3. Root of a directory structure, in Maven repository layout, that
   contains the artifacts to be deployed

Closes gh-25107

Closes gh-25282

Closes gh-25337

Closes gh-25336

Closes gh-25335

Closes gh-25334

Closes gh-25285

Closes gh-25281