Closes gh-22721

* gh-21388:
  Polish "Test the launch script when executed directly"
  Test the launch script when executed directly

Closes gh-21388

See gh-21388

See gh-21388

See gh-22709

Closes gh-22711

Closes gh-22709

Closes gh-22706

Closes gh-22705

* pr/22704:
  Fix broken links to Micrometer registry docs

Closes gh-22704

See gh-22704

Prior to this commit, the livenessState and readinessState health
indicators would not be configured automatically and would be missing
from the "liveness" and "readiness" health groups, leading to 404s when
hitting the `/actuator/health/liveness` or `/actuator/health/readiness`.

This commit ensures that the health indicators beans have the proper
name and revisits the auto-configuration conditions to reflect that as
well.

Fixes gh-22562

* gh-22631:
  Polish "Document properties to enable probe health indicators"
  Document properties to enable probe health indicators

Closes gh-22631

See gh-22631

Document property names to enable probe(readiness/liveness)
health indicators.

See gh-22631

Closes gh-22686

* gh-22681:
  Polish "Look in correct context when finding Liquibase beans"
  Look in correct context when finding Liquibase beans

Closes gh-22681

See gh-22681

See gh-22681

See gh-22645

Closes gh-21570

Closes gh-22094

Fixes gh-21606

Closes gh-22672

Fixes gh-19471

Closes gh-22669

Closes gh-15977

Closes gh-22665

Closes gh-22565

Closes gh-22656

Closes gh-22655

Closes gh-22659

Closes gh-22645

Closes gh-22650

The overhead of build scans seems to have brought us right to the limit
of the Maven JVM's heap. As a result, builds are occasionally failing
as the heap's been exhausted.

This commit increases the JVM's max heap.

Closes gh-22649

Closes gh-22641