[depre] Deprecate strict-types rules as risky and not practical

[TomasVotruba]

Revisiting couple rules I've added in #955 that are risky as assuming inner empty type. These rules were made to resolve https://github.com/phpstan/phpstan-strict-rules. As Rector moves to more practical rather academical area, these ruels would be best fit in own niche community ruleset.

Now we have better, more stable strategy to improve code quality like:

• levels: https://getrector.com/documentation/levels
• follow by prepared sets: https://getrector.com/documentation/set-lists

Those should be used instead to have upgrade path under control.

The only practical rule remains - DisallowedEmptyRuleFixerRector. It might need split to multiple tailored rules, but works well for now. This one is already part of code quality set 👍

[samsonasik]

we don't know what "this rule" is, should mention self::class instead.

[TomasVotruba]

What's the output error? I think deprecated rules are reported on Rector run.

[samsonasik]

this show:

          "/home/runner/work/CodeIgniter4/CodeIgniter4/app/Config/Mimes.php"     
         file, due to:                                                          
         "System error: "This rule is deprecated and will be removed as risky   
         and requires manual checking"                                          
         Run Rector with "--debug" option and post the report here: https://github.com/rectorphp/rector/issues/new". On line:
         62                       

see https://github.com/codeigniter4/CodeIgniter4/actions/runs/18720569673/job/53391545753#step:12:48

[TomasVotruba]

Last item:

Feel free to update the message though 👍

[samsonasik]

I see, that seems fine then 👍