Update to Symfony 6.4

Ok, so the first let's-see-what-breaks-run stops at PHPStan complaining about https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.4.md#dependencyinj....

Let's see if anything else breaks if we temporarily suppress all of these deprecations by adding them to core/phpstan-baseline.neon.

What Have We (or at least I) Learned So Far:

- SF6.4 deprecates ContainerAwareTrait and ContainerAwareInterface.
This affects:

core/lib/Drupal/Core/Access/CheckProvider.php                       
core/lib/Drupal/Core/Cache/CacheFactory.php                           
core/lib/Drupal/Core/Cache/CacheTagsInvalidator.php                 
core/lib/Drupal/Core/Cache/ChainedFastBackendFactory.php            
core/lib/Drupal/Core/Cache/Context/MenuActiveTrailsCacheContext.php  
core/lib/Drupal/Core/DependencyInjection/ClassResolver.php          
core/lib/Drupal/Core/DrupalKernelInterface.php                  
core/lib/Drupal/Core/Entity/EntityTypeManager.php                   
core/lib/Drupal/Core/EventSubscriber/KernelDestructionSubscriber.php  
core/lib/Drupal/Core/Logger/LoggerChannelFactory.php                 
core/lib/Drupal/Core/Queue/QueueFactory.php                           
core/lib/Drupal/Core/StackMiddleware/Session.php                    
core/lib/Drupal/Core/StreamWrapper/StreamWrapperManager.php         
core/lib/Drupal/Core/Update/UpdateHookRegistryFactory.php           
core/lib/Drupal/Core/Update/UpdateRegistryFactory.php                 
core/modules/book/src/Cache/BookNavigationCacheContext.php          
core/modules/media_library/src/OpenerResolver.php                   
core/modules/system/tests/modules/render_placeholder_message_test/src/RenderPlaceholderMessageTestController.php  
core/modules/system/tests/modules/service_provider_test/src/TestClass.php  
core/tests/Drupal/Tests/Core/Controller/ControllerResolverTest.php  
core/tests/Drupal/Tests/Core/DependencyInjection/DependencySerializationTest.php  
core/tests/Drupal/Tests/Core/Utility/CallableResolverTest.php

Out of those

core/modules/book/src/Cache/BookNavigationCacheContext.php          
core/lib/Drupal/Core/Cache/Context/MenuActiveTrailsCacheContext.php  

seem likely candidates for becoming Service Subscribers?

- ComponentsIsolatedBuildTest doesn't like stability lowering
- ComposerProjectTemplatesTest::testTemplateCreateProject seems to have problems with putting the set stability level into the version string.
- ComposerProjectTemplatesTest::testMinimumStabilityStrictness seems to be having problems with not finding any 'dev' stability level since they are all in the excluded-from-comparing drupal/core.
EDIT: Seems like \Composer\Semver\VersionParser::parseStability doesn't parse SF's verion-string of 6.4.x-dev 3f5752f correctly and returns it as stable (#3392814: testMinimumStabilityStrictness struggles with dev versions )

Rebased as-is.

Can I have some "blessing" on splitting off an issue for converting BookNavigationCacheContext and MenuActiveTrailsCacheContext into lazy services?

This won't do much with the whole ContainerAware deprecation, it just shifts it to another point.
But by the looks of it, these two services are ContainerAware just for the lazy loading, and looking at the time of creation of both, we didn't really have the lazy services concept up and running.
For consistency reasons, I think we should convert them into those, but unsure if the people in here agree, since we of course have to do a lot of construct deprecation dancing.

For all the other deprecations, I agree with @catch in #8:

so I think we need to fork ContainerAwareTrait or otherwise keep things more or less the same for that.

Forking ContainerAwareTrait into core seems the only way to me. As far as I can see all deprecation added in this issue come from this deprecation, so there's not much to split IMHO, but happy (and easy) to be convinced otherwise :)

Created child issues, remove tag.

Damn keeping tabs open for too long and not refreshing!

Sorry, also reverted the version back to 10.2.x-dev.