As our tooling improves, it might be worth considering applying phpcbf to all files across Moodle (in batches).

In the long run, this will help us to keep code compliant with our coding style as it becomes easier, and easier, to fix issues discoverd.

I would suggest that we:

1. identify any sniffs which should be able to, but currently do not support, the auto-fix feature and add that ability
2. start with some low-churn targets and apply fixes
3. build up to higher churn locations

Once this has been done across the entire codebase, we should look at running phpcbf with our ruleset during GHA, and via TOBIC for all files changes in a patchset.