fix: resolve typo in authMethod enum cases

[hendrikheil]

Summary

We just worked with Nextcloud webhooks. We noticed that the OpenAPI specification defines the authMethod which uses headers for authentication as headers. This seems to be a typo in both the OpenAPI spec as well as the docblocks inside the code itself. The AuthMethod enum itself defines the cases Header and None, which map to header (singular) and none respectively.

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]

Indeed, this is wrong!

[provokateurin]

/backport to stable31

[provokateurin]

/backport to stable30

[provokateurin]

/backport to stable29

[provokateurin]

@hendrikheil You need to run ./build/openapi-checker.sh and amend the result to the commit.

[come-nc]

This needs a force-merge as it comes from a fork.

[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.)

[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

[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/51449/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 90872660 7ac3fa7e

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

Error: Failed to check for changes with origin/stable29: No changes found in backport branch

---

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

[provokateurin]

Backport to 29 was wrong because the app was only added in 30 :)