The JobLauncherCommandLineRunner reassigned method arguments inside the
merge method. Instead of reassigning the method argument just return
the new instance directly.

Also some minor cleanup (unnesseccary null check and continue keyword).

Closes gh-10612

* pr/10774:
  Remove static Boot version from documentation

Closes gh-10774

Closes gh-10626

Closes gh-10727

Closes gh-10730

Closes gh-10729

Closes gh-10728

Closes gh-8899

Closes gh-7999

Closes gh-10709

Closes gh-10687

Closes gh-10651

* gh-10635:
  Fix typo in documentation

- As error handling sample is using `CustomErrorType`, fix
  description which mentions `CustomerErrorType`.

Closes gh-10632

Closes gh-10631

Closes gh-10630

Closes gh-10629

* gh-10588:
  Polish "Provide informative reason when rejecting request with invalid level"
  Provide informative reason when rejecting request with invalid level

See gh-10588

Previously, bad request with no reason was included in the response.
This commit introduces the reason when invalid log level is sent in the
request.

Fixes gh-10588

* gh-10554:
  Honor logging.path config in filePattern for Log4j2 RollingFile

Previously, rolled over files were always written to logs/. This
commit ensures that rotated logs are written into the directory
specified in the application config's logging.path property.

Closes gh-10554

Closes gh-10606

Previously, if Undertow failed to start, some of Undertow's
internal components would have been started but the started field of
UndertowEmbeddedServletContainer remained false. This meant that when
stop() was called nothing was done as the container believed it had
not been started.

This commit updates UndertowEmbeddedServletContainer to stop both the
DeploymentManager and the Undertow instance in start() if an exception
is thrown. This aligns the behaviour of
UndertowEmbeddedServletContainer with that of the Tomcat equivalent.

Closes gh-10528

Closes gh-10561

See gh-10561

This commit clarifies the scope of the datasource initializr. In
particular, it is not possible to create the schema with that facility
and let Hibernate creates additional tables.

Closes gh-9048

Previously, if the file watcher thread tried to stop the
FileSystemWatcher when another thread was already stopping it a
livelock could occur. The livelock occurred because the file watcher
thread would attempt to lock a monitor that was being held by a thread
that had joined the file watcher thread and was waiting for it to die.

This commit avoid the livelock by narrowing the synchronization that's
used when stopping the FileSystemWatcher. The monitor is used to
obtain a reference to the file watcher thread in a thread-safe manner,
but it is released prior to joining the file watcher thread and
waiting for it to die. This will allow a parallel attempt by the
file watcher thread to stop itself to succeed.

Closes gh-10496

Closes gh-10484

Closes gh-10483

Closes gh-10482

Closes gh-10481

See gh-10475
See gh-10473