fix(SetupChecks): Pass webfinger if the handler returns 400 too

[joshtrichards]

• Resolves: Wrong webfinger incorrect report on docker image social#864
• Fixes 0.6.0beta1: /index.php/.well-known/webfinger → Actor not found social#1604

Summary

When running a check against /.well-known/webfinger in a stock install the checks are fine, but when an actual webfinger handler is installed (like the social app) the return code is going to be 400 per the spec¹ since the setup check isn't providing a ?resource value (and we're not going to).

Semi-related: nextcloud/social#1951 (because we were returning a 500 error since our check doesn't pass a resource value and now once merged that'll return a 400 as per the spec; though our checks obviously wouldn't have passed either way).

TODO

• ...

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)

Footnotes

1. https://datatracker.ietf.org/doc/html/rfc7033#section-4.2 ↩

[joshtrichards]

/backport to stable30

[joshtrichards]

/backport to stable29

[joshtrichards]

/backport to stable28