Closes gh-23745

This reverts commit c4a5a347.

See gh-23721

Closes gh-23742

Closes gh-23744

Closes gh-23743

Previously, the shutdown hook was only registered once refresh has
completed. If the JVM was shut down during refresh (or after refresh
and before the hook was registered) the hook wouldn't run and the
partially refreshed context would not be cleaned up.

This commit moves the registration of the shutdown hook to before
refresh processing begins. This ensures that the hook is available
to clean up the context if the JVM is shutdown while refresh is in
progress.

Fixes gh-23625

* pr/23737:
  Fix links to Spring Framework documentation

Closes gh-23737

See gh-23737

Closes gh-23732

Fixes gh-23527

* pr/23720:
  Polish

Closes gh-23720

See gh-23720

Closes gh-23721

See gh-23693

Closes gh-23731

This commit modifies the documentation generated for the
Maven plugin to include links to javadoc when Spring
Boot types are mentioned. Some javadoc was also polished
to improve the generated docs.

Fixes gh-21555

This reverts commit 9460d74e.

Fixes gh-23724

Closes gh-23722

Closes gh-23725

* pr/23693:
  Polish "Fix detection logic for embedded databases"
  Fix detection logic for embedded databases

Closes gh-23693

See gh-23693

See gh-23693

There's a bug in some versions of AsciidoctorJ where extensions are
only called on this first conversion performed by a given Asciidoctor
instance. This affects the multi-page documentation where there are
multiple conversions performed – one for each page in the
documentation.

This commit upgrades the version of AsciidoctorJ used by the
Asciidoctor Gradle plugin to 2.4.1, which contains fix for the problem.

Closes gh-23709

Closes gh-23718

Closes gh-21536

Closes gh-23715

* pr/23633:
  Polish 'Add a FailureAnalyzer for ConfigDataNotFound'
  Add a FailureAnalyzer for ConfigDataNotFound

Closes gh-23633

See gh-23633

Add a `FailureAnalyzer` to deal with `ConfigDataNotFoundException`.

See gh-23633

Refactor `ConfigData` processing code to make it less awkward to
follow.

Prior to this commit the `ConfigDataLocationResolver` would take a
String location and return a `ConfigDataLocation` instance. This was
a little confusing since sometimes we would refer to `location` as the
String value, and sometimes it would be the typed instance. We also
had nowhere sensible to put the `optional:` prefix logic and we needed
to pass a `boolean` parameter to a number of methods. The recently
introduced `Orgin` support also didn't have a good home.

To solve this, `ConfigDataLocation` has been renamed to
`ConfigDataResource`. This frees up `ConfigDataLocation` to be used
as a richer `location` type that holds the String value, the `Orgin`
and provides a home for the `optional:` logic.

This commit also cleans up a few other areas of the code, including
renaming `ResourceConfigData...` to `StandardConfigData...`. It also
introduces a new exception hierarchy for `ConfigDataNotFoundExceptions`.

Closes gh-23711

Update `SpringApplication` so that `FailureAnalyzers` apply even if
the `ApplicationContext` was not created. If no `ApplicationContext`
is available, only `FailureAnalyzer` instances that do not implement
any `Aware` interfaces are considered.

Closes gh-23710

Previously, when building a layered jar with Gradle, project
dependencies were treated the same as any other dependency, being
included in the dependencies or snapshot dependencies layer based
on their version.

This commit updates the default layering when using Gradle to include
project dependencies in the application layer by default. The DSL has
also been updated to allow their layer to be customized using new
includeProjectDependencies() and excludeProjectDependencies() methods
rather than relying on including and excluding them via a
group:artifact:version pattern.

Closes gh-23431

Closes gh-23702

Closes gh-23701

Closes gh-23700

Fixes gh-23699