feat(collectives-publish) static site update endpoint

[kjoscha]

📝 Summary

The external build service of the publish feature sends back a success (or error) message to Collectives after a build ran or failed. The payload is expected as the following:

{ "status": "published",
  "data": {
    "publish_url": "https://publish.schnubbel.com/publish/<static_site_id>"
  }
}

or in case of failure

{ "status": "failed",
  "data": {
    "error_message": "<some error message>"
  }
}

🏁 Checklist

• API endpoint exist and is tested

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI tools
• The AI-generated content was reviewed, comprehended and tested by a human

Testing manually

You can tiun a manually update from the terminal via curl like this (replace the static site id):

curl -X PATCH "http://localhost/ocs/v2.php/apps/collectives/api/v1.0/p/static-sites/01a1112f-7cb5-747a-be61-07c74093449a" \
  -H "Host: nextcloud.local" \
  -H "OCS-APIREQUEST: true" \
  -H "Content-Type: application/json" \
  -d '{"status": "published", "data": {"publish_url": "https://example.com/site"}}'

[code4candy]

description seams to be added manually - this file gets created automatically by executing:
composer run openapi
--> related test in CI pipeline also failed

[code4candy]

plz fix ci tests:

• Lint php-cs / php-cs
• OpenAPI / openapi (see above)

[code4candy]

Commit-Message:
Betreff und Trailer sind mit 4 Leerzeichen eingerückt ( feat(publish): …). Damit erkennen commitlint und Changelog-Tools den Conventional-Commit-Typ nicht, und die Trailer werden möglicherweise nicht als Trailer erkannt