feat(psalm): Mark all usage of deprecated code as error

[provokateurin]

Summary

Based on #52853.

The idea is to prevent any new code to use already deprecated stuff. It will not be possible everywhere since we sometimes have no replacement, but then it should just be added to the baseline.
This change adds a lot to the baseline, but it's basically just a todo list for technical debt cleanups :)

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[ChristophWurst]

PR authors will hate Psalm and not the reviewer who points these out. I'm in 👍

nit: semantic commit is ci or chore but not feat as there is no new feature added to the product 🤓

[joshtrichards]

This (and thus checked baselines) suppress for lib and thus lib/private. Am I understanding? I don't see coverage of OC\ between the various psalm configs.

[come-nc]

This (and thus checked baselines) suppress for lib and thus lib/private. Am I understanding? I don't see coverage of OC\ between the various psalm configs.

Yes, because lib/private needs to use the deprecated interfaces in a lot of cases (often the new implementation calls the deprecated one).
So it’s only an issue when deprecated methods/constants/classes are used outside of lib, in lib it’s a case by case situation.