Co-authored-by: Daniel García <dani-garcia@users.noreply.github.com>

Updated diagnostics page

- Added reverse proxy check
- Better deffinition of internet proxy
- Added SQL Server version detection

`push` only counts for pushes to branches on the repo, not forks

It's not incorrectly wrapped. We care about the return type being `Option`.

https://rust-lang.github.io/rust-clippy/master/index.html#upper_case_acronyms

https://rust-lang.github.io/rust-clippy/master/index.html#from_over_into

Return generic message when Send not available

Sync global_domains.json

Reference: https://github.com/messense/rust-musl-cross/pull/34

This should help avoid leaking information about (non)existence of Send
and be more in line with what official server returns.

Add support for the Disable Send policy

Upstream refs:

* https://github.com/bitwarden/server/pull/1130
* https://bitwarden.com/help/article/policies/#disable-send

CORS fixes

Send access check fixes

Adjust checks for max access count, expiration date, and deletion date.
The date checks aren't that important, but the access count check
currently allows one more access than it should.

This is only implemented for the database specific structs, which is not what we want

* The Safari extension apparently now uses the origin `file://` and expects
  that to be returned (see bitwarden/browser#1311, bitwarden/server#800).

* The `Access-Control-Allow-Origin` header was reflecting the value of the
  `Origin` header without checking whether the origin was actually allowed.
  This effectively allows any origin to interact with the server, which
  defeats the purpose of CORS.