Issue: SPR-11272

Issue: SPR-11259
(cherry picked from commit f0d21510)

Issue: SPR-11251

Issue: SPR-11251

Issue: SPR-11246

Issue: SPR-11221

Issue: SPR-11002
(cherry picked from commit 8d6d6be3)

(cherry picked from commit 2a52decb)

(cherry picked from commit 519f78c3)

Fix CacheAspectSupport to consider a cache hit from any of the multiple
@Cachables that may have been specified using the @Caching annotation.

Prior to this commit the following scenario would never produce a hit:

    @Caching(cacheable = {
            @Cacheable(value = "c1", unless = "#result.size() < 4"),
            @Cacheable(value = "c2", unless = "#result.size() > 3")
     })

Issue: SPR-11124

Issue: SPR-11039
(cherry picked from commit 0aedd81c)

Perform setParent's Environment merging for ClassPathXmlApplicationContext etc constructors with parent argument as well

Issue: SPR-11068
(cherry picked from commit c5fcf195)

As a side effect, @Bean overrides and overloads work with 'allowBeanDefinitionOverriding'=false as well now.

Issue: SPR-10992

Since @Bean methods are never used with externally specified constructor argument values but rather just with autowiring, the non-lenient constructor resolution mode is appropriate in case of an overloaded @Bean method, not performing any type difference weight checks. This change includes a refinement of Spring's existing non-lenient constructor resolution (which needs to be explicitly turned on and is therefore not well tested), narrowing the conditions for the ambiguity check (only in case of the same number of arguments and not for overridden methods).

Issue: SPR-10988
(cherry picked from commit b093b849)

Update `AbstractApplicationEventMulticaster` to support `EventObjects`
with a null source (which can happen if they have been serialized).

Issue: SPR-10945
(cherry picked from commit b0ff834e)

Ensure that property source locations are processed in the same order
regardless if the 'name' attribute is set or not.

Prior to this commit multiple locations from a `@PropertySource` with
a name were added to a `CompositePropertySource` in such a way that
the first location would take precedence. This has now been reversed
for consistence with unnamed `@PropertySource`s

Issue: SPR-10820
(cherry picked from commit e3d3d8cd)

Issue: SPR-11027
(cherry picked from commit 4675bc4e)

Issue: SPR-11032
(cherry picked from commit 8bd48044)

Issue: SPR-10974
(cherry picked from commit 7a9d5837)

Exclude self @Component when parsing @ComponentScan annotations.

Issue: SPR-10531
(cherry picked from d91ffb)

(cherry picked from commit 52cca48f)

Issue: SPR-10931
(cherry picked from commit 7bc3e3b3)

(cherry picked from commit facf31f0)

(cherry picked from commit caa1218d)

(cherry picked from commit 465e6292)

Restoring consistency with AnnotationConfigApplicationContext.

Issue: SPR-10852
(cherry picked from commit 01b8d932)

(cherry picked from commit e812b6ce)

Issue: SPR-10788

PropertySourcesPlaceholderConfigurer's "ignoreUnresolvablePlaceholders" setting reliably applies to nested placeholders as well

Issue: SPR-10549
(cherry picked from commit 127b91fd)

Issue: SPR-10609