[Renaming] Add RenameCastRector

[mttsch]

While there is already RealToFloatTypeCastRector to handle the deprecation of the (real) cast, this generalized rector rule will allow to configure the cast renaming and thus also support other types of cast renamings.

[mttsch]

Background: PHP 8.5 will most likely deprecate further non-standard casts, see https://wiki.php.net/rfc/deprecations_php_8_5#deprecate_non-standard_cast_names.

In preparation, I already submitted a patch to nikic/php-parser (nikic/PHP-Parser#1098) to get the kind of cast for bool, string, and int casts so that once that a new version of nikic/php-parser is released with this cast kind information and the cast deprecations in PHP 8.5 are official, this new rector can be used. (The double cast could already now be implemented.)

Additional side information: I have already prepared locally quite a few branches for other changes from this deprecation RFC that are likely to pass. Please inform me whether I could already open PRs for them to signal to other contributors that they were already implemented and you can merge then whenever you want or do you want me to wait until a future point in time to open them?

[calebdw]

While there is already RealToFloatTypeCastRector to handle the deprecation of the (real) cast,

Why not rename that rule and make it configurable then?

[mttsch]

@calebdw Good question, that is a point I wanted to ask, too, but forgot.

I do not know how rector handles BC with rector rules. Renaming the real cast rector could break existing code. It could be deprecated and the PHP 7.4 set could use this rector instead, I guess.

[mttsch]

I was wondering whether this is okay, to directly expose PHP parser class names in value objects. This avoids having to add a mapping layer between the value passed here and the cast class.

[TomasVotruba]

Great idea, thank you 👍

Could you replace RealToFloatTypeCastRector with this rule in our configs in follow-up PR?

[mttsch]

@TomasVotruba Yes, see #7136