Add Suport symfony 8 and php 8.5

[eerison]

Add Suport symfony 8 and php 8.5

I am targeting this branch, because {reason}.

Related: #1837

Changelog

### Added
- Added support Symfony 8
- Added support php 8.5

### Removed
- Removed Support Symfony 7.2

To do

• Add suport symfony 8 on composer.json
• Fix pipelines for symfony 8
• Revert symfony cmf composer chnages (blocked by Add mixed value like ConstraintValidatorInterface symfony-cmf/routing-bundle#498)
• Copy commits from Devkit
• Fix phpstan on php8.5 (Add Suport symfony 8 and php 8.5 #1841 (comment))
• Symfony 8 blocked by Add support for Symfony 8 SonataDoctrineORMAdminBundle#1852
• Revet deleted test (blocked by [Panther] Crawler::closest method changed return type to static symfony/symfony#62624)

[eerison]

hmmm any idea which approach I could use in this case:

we are using : Symfony\Component\PropertyInfo\Type, But in Symfony 8 it was replaced to Symfony\Component\TypeInfo\Type.

@dmaicher any idea?

[dmaicher]

hmmm any idea which approach I could use in this case:

we are using : Symfony\Component\PropertyInfo\Type, But in Symfony 8 it was replaced to Symfony\Component\TypeInfo\Type.

@dmaicher any idea?

I guess we can just ignore those errors? PropertyTypeExtractorInterface::getTypes was also removed on Symfony 8 so it won't be called anyway.

[eerison]

PropertyTypeExtractorInterface

now I get what you mean 😄 , getTypes is not used anymore. then yeah I guess we are safe to remove this method too.

should I add deprecation trigger, or just NEXT_MAJOR is fine?

[eerison]

Should I strict on ^3.1.2 or keep it more flexible in ^3.0?

the problem detected was more related with symfony-cmf then page bundle.

[eerison]

I do not know if it could be related with phpstan/phpstan-symfony#322

like we are doing on https://github.com/sonata-project/SonataPageBundle/blob/4.x/phpstan-baseline.neon#L22

But I would prefer ignore those errors besides add workaround for code that never going to be used. like this getType as null.

we add checks to verify if it's null or not, But it is a field that should be filled, otherwise some places wont work, like phpstan says.

if this field is null, the code will break for sure.

My suggestion is, ignore those errors and create a issue to solve this mess, it will make our life easier.

and I remember it was painful for this PR: #1522

let me know what you think and I could open a issue.

[eerison]

should I create another file to not mix with this one?