See gh-21615

See gh-21615

* pr/22777:
  Polish "Propagate the cause that led Reactor"s debug agent to fail"
  Propagate the cause that led Reactor"s debug agent to fail

Closes gh-22777

See gh-22777

Prior to this commit, DebugAgentEnvironmentPostProcessor throws a
RuntimeException with a generic error message if its initialization
fails. The causing exception is discarded, which makes error analysis
unnecessarily difficult.

This commit attaches the cause to the newly thrown RuntimeException.

See gh-22777

Closes gh-22490

Closes gh-22763

Closes gh-22281

Closes gh-22752

Closes gh-22755

Closes gh-20920

Previously, the endpoints' responses could occasionally exceed
WebClient's in-memory buffer limt, for example if the threads endpoint
was reporting a large number of threads or the threads had large
stacks.

This commit disables WebClient's in-memory buffer size limit so that
the tests passing is not dependent on the size of the endpoints'
responses.

Closes gh-22743

Previously, waitsForQuietPeriod would iterate 10 times, touching a new
file and then sleeping for 100ms at it did so. With a quiet period of
200ms, this was intended to result in a single change set containing
10 files. However, the test would fail occasionally as multiple change
sets were detected. The test is multi-threaded and is, therefore, at
the mercy of the scheduler. If the thread that is iterating and
touching the files takes over 200ms to be scheduled – exceeding the
watcher's quiet period – the watcher may detect a change set while the
changes are still being made. Eliminating this possibilty would require
the test to participate in the watcher's synchronization, which would
require some changes to its implementation. Instead, this commit
aims to avoid the problem by sleeping for 1/10 of the time (10ms) and
expecting a single change set of 100 files. The hope is that the much
shorter sleep time will result in the file touching thread being
scheduled well within the 200ms quiet period.

Closes gh-22732

Closes gh-22717

Closes gh-22723

Closes gh-22717

* 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-22709

Closes gh-22705

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

Closes gh-22704

See gh-22704

* 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

Fixes gh-19471

Closes gh-15977

Closes gh-22565

Closes gh-22655

Closes gh-22659

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