[Coding Style] Enable rule PSR12.Files.FileHeader + unify file headers

[michalkleiner]

Description:

While applying the CS rule to fix spacing around file headers I noticed there are some inconsistencies, so I've also bulk unified them across the codebase since we were already updating over 2000 files just for the CS rule.

We will add the commit to the .git-blame-ignore-revs file as well so it's fitting to update all the headers at once as well.

I reviewed all the files manually before committing them using local git UI (Fork) and I can confirm the change is safe and doesn't alter any functionality.

Main changes:

• new line additions around file headers
• changing http to https in file headers
• tweaking spacing in file headers
• rebuilding dist files as the file headers are included in the dist files as well

Review

• Functional review done
• Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• Documentation added if needed
• Existing documentation updated if needed

[sgiehl]

This one actually isn't reviewable at all. GitHub does not even support to show so many changes.
If you want to have that reviewed, I guess you might need to split up the PR like I did it with this one: #21926

[michalkleiner]

Thanks for the feedback Stefan.
As I expected that, it was why I've written in the description that I reviewed the files locally to try and alleviate that concern. I've actually looked at all the files one by one as it's quite easy to see relatively quickly that only one or two lines were added at the same place in each file, so it was basically just hitting enter to stage the files one by one and only very small handful of files needed manual intervention. I also committed the changes in separate commits to help with that. Yes, we can split the PR into 10 smaller ones as you did before, I can do that if that makes it easier to get that through, but I'm not sure it's time well spent. Alternatively, it's also possible to view the change in local git gui. Let me know what you prefer.

[sgiehl]

@michalkleiner For future PRs of that size it would be better to have smaller chunks. For that one I guess we simply leave it as is. I only had a look through the changes at random. As it's no easily possible to look through such big commits at once without loosing focus 🙈
Btw. For having unified headers across all files it could maybe be useful to create a custom sniff somewhen in the future.