Diagnostic check should recognize that none is equivalent to noindex, nofollow

[BeansIsFat]

The current diagnostic check for HTTP Response validation reports errors when x-robots-tag does not contain noindex or nofollow. These errors are even reported when x-robots-tag contains none which is equivalent to noindex, nofollow. So the user falsely thinks their configuration fails to have the recommended robots protection intended by the developer.

[BlackDex]

The check we mainly do is to see if the headers Vaultwarden sets are removed or modified. Which in your example is the case. If we for some reason need to adjust something, and the headers are modified by something, we can't guarantee a good working environment anymore.

So, the check and outcome is valid, while the value might be the same in the end result, it's not the recommended way.