Use OC namespace for core ReponseDefinitions instead of OCA

[JulienFS]

Summary

It looks like #36666 and #39331 lead to having a core file in the OCA namespace. To my understanding, OCA is for apps, while OC\Core is for core.

TODO

• check that there's no magic involved with namespaces regarding OpenAPI and that these changes are an applicative NOOP

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[provokateurin]

Thanks for catching this!

[provokateurin]

/backport to stable29

[provokateurin]

/backport to stable28

[provokateurin]

Your commit should probably start with fix(core): (and you can just squash them).

[provokateurin]

@JulienFS please fix the CI (code checkers and lint php-cs)

[JulienFS]

Performance and cypress don't seem to pass. At first sight I don't know what to do. Should I try to fix them or is it somehow out of my hands ?

[provokateurin]

No those are flaky sometimes. I just gotta restart cypress until it works (and performance is not required to pass)

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[provokateurin]

The CI on this PR seems to be really unlucky 😞

[welcome]

Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

[nickvergessen]

/backport to stable29

[backportbot]

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/45509/stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2d84d0f5

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45509/stable28

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/45509/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2d84d0f5

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45509/stable29

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/45509/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2d84d0f5

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45509/stable29

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.