chore(ci): Switch to setup-php@verbose version due to stuck runs

[DerDreschner]

At least @SebastianKrupinski and myself experienced some workflow runs where the set up php step stuck. As discussed in the talk channel, this seem to affect more people from within the company. It also happened today with the setup-nextcloud workflow action from @ChristophWurst , which tags @v2 and therefore already uses the latest version:

To be able to find the root cause for that issue, I've decided to switch the daily workflows to the @verbose version (see: https://github.com/shivammathur/setup-php?tab=readme-ov-file#verbose-setup). It might be worth to do that for the setup-nextcloud workflow as well, to get more verbose logging on possibly stuck runs faster.

[SebastianKrupinski]

@DerDreschner Had a look the changes, they look right... the CI run is the true test tho... I am surprised that some of those action versions where not updated by dependabot

[ChristophWurst]

Edit: I've removed the last two steps (Check openapi*.json [...] and Show changes on failure) from the openapi template as it fails on our repository. They were not included before anyway here (why?).

We try not to commit artifacts. They bloat the repository, you have to keep source and artifact in sync and it can lead to additional conflicts. Therefore we just generate these files when the package is built.

[DerDreschner]

We try not to commit artifacts. They bloat the repository, you have to keep source and artifact in sync and it can lead to additional conflicts. Therefore we just generate these files when the package is built.

Ahh, I see! I consider that best-practice to be honest and didn't expect the template repo to promote that with any workflows. Thanks!

[kesselb]

The version bumps for the other actions are unrelated; remove those.
See #12137 for context.

[DerDreschner]

The version bumps for the other actions are unrelated; remove those.

Done.