Psalm use new baseline in action

[rinkp]

What would you like?

We should use the new Psalm baseline when running a GitHub action.
Why? We continuously have to update the baseline and then PRs cannot be merged

PR reviewers can see that the baseline has changed and should manually deny PRs for which there is an unnecessary baseline change

Why is this needed?

No response

Other information

No response

[tomudding]

I actually think Psalm does not support the usage of two baselines like PHPStan does. So we should probably not try to generate a baseline.