fix(settings/SetupChecks): Don't follow redirects

[marcelklehr]

Summary

In some cases the reverse proxy config redirects to login when accessing unknown URLs like .ocdata. Login, however, returns a HTTP 200, which is taken to be a failure by the datadirectory protection setup check.

• Is this a good idea?

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)

[susnux]

I think not following is a bad idea as there could be a redirect that still resolves to the data directory.
Instead we should check for the final response body content?

[come-nc]

I agree with Ferdinand it makes sense to follow redirects, at least for some tests.
But this test is too fragile and should be improved.

Maybe we should add content to .ocdata and check that the content is part of the response? (maybe it’s time to rename that file also)

[susnux]

See #46456