Closes gh-26842

Closes gh-26762

Closes gh-26772

Closes gh-26770

Closes gh-26763

Closes gh-26771

Closes gh-26620

Closes gh-26836

Closes gh-26835

Closes gh-26834

Closes gh-26833

Closes gh-26832

Closes gh-26831

Closes gh-26830

Closes gh-26829

Closes gh-26760

Closes gh-26826

Fixes gh-26812

Closes gh-26822

Change `CompositeHealth.getDetails()` to public so that it serializes
correctly when `MapperFeature.CAN_OVERRIDE_ACCESS_MODIFIERS` is
disabled.

Fixes gh-26797

Closes gh-26791

Closes gh-26790

Closes gh-26789

Closes gh-26788

Closes gh-26787

Closes gh-26786

Closes gh-26785

Closes gh-26784

Closes gh-26783

Allow groups to be used with standard locations so that order of
profile-specific files is consistent.

Prior to this commit, the default search locations considered for
application properties/yaml files was the following:

	optional:classpath:/
	optional:classpath:/config/
	optional:file:./
	optional:file:./config/
	optional:file:./config/*/

Each of these locations was independent which could cause confusion
if certain combinations were used. For example, if profile-specific
files were added to `classpath:/` and `classpath:/config/` then the
latter would always override the former regardless of the profile
ordering.

This commit updates `StandardConfigDataLocationResolver` so that a
group of locations can be specified for each item. This allows us to
define the following set of search locations which provide more logical
ordering for profile-specific files

	optional:classpath:/;optional:classpath:/config/
	optional:file:./;optional:file:./config/;optional:file:./config/*/

Closes gh-26593

Closes gh-26781