advise against using 443 for bridge ORPort

Currently, guides for setting up bridges either recommend using 443 for ORPort (archlinux, dragonflybsd, freebsd, netbsd, openbsd, opensuse), or recommend only against 9001 (all others guides from what I can tell).

I setted up some bridges recently, and used 443 as ORPort on some, and other values on others. After about five days of running, most of the 443 bridges got tagged "tor" by Shodan, presumably because Tor TLS handshake is quiet noticeable with its odd subject CN and issuer CN.

Ideally Tor would support not having a publicly reachable ORPort when running as bridge, but until it's possible (as far as I know, it fails reachability test and doesn't submit its descriptor), I believe the recommended configuration should be one that makes it unlikely to be detected, at least advising against port 443 or other ports commonly used for TLS, and maybe recommend using a random, high (non-service) port, so it's unlikely to get scanned by accident.