Update symfony packages

[melroy89]

• Update to Symfony v6.4
• Ran symfony/security-bundle recipe
• Ran symfony/framework-bundle recipe + enable annotation for Mbin

[nobodyatroot]

Verified update goes smoothly, no issues on my end.

[e-five256]

A few instance owners mentioned receiving this error spamming their logs and growing messenger async/async_ap queues after applying this PR:

{"message":"Error thrown while running command \"messenger:consume async_ap -vv --time-limit=1800\". Message: \"Typed property Symfony\\Component\\PropertyInfo\\Type::$class must not be accessed before initialization\"","context":{"exception":{"class":"Error","message":"Typed property Symfony\\Component\\PropertyInfo\\Type::$class must not be accessed before initialization","code":0,"file":"/var/www/kbin/vendor/symfony/property-info/Type.php:134"},"command":"messenger:consume async_ap -vv --time-limit=1800","message":"Typed property Symfony\\Component\\PropertyInfo\\Type::$class must not be accessed before initialization"},"level":500,"level_name":"CRITICAL","channel":"console","datetime":"2023-12-06T16:34:10.250453+00:00","extra":{}}

It seems so far running bin/post-upgrade or clearing caches manually (specifically php bin/console cache:clear or docker compose exec php bin/console cache:clear if containerized) has helped stop the errors and fix queues