Fix http host/origin allowlist never matching configured values

[echennells]

is_allowed_host/is_allowed_origin compared the request host (normalized via to_normal_host, which substitutes default_port when the port is zero) against the raw configured endpoints in options_.hosts/origins, which are not normalized. A configured value without an explicit port (e.g. host = localhost) therefore never matched any request because the request side carried default_port (80/443) while the configured side carried port 0.

Compare against host_names()/origin_names() instead, which apply the same to_lower(default_port) normalization to the configured values, so both sides are symmetric.

Verified on a node: with host = localhost configured, Host: localhost is now accepted (was rejected), while non-listed hosts are still rejected.

[evoskuil]

This is at least the third time we have hit a namespace conflict due to xcode polluting the global namespace with a common word.

/Users/runner/work/libbitcoin-network/libbitcoin-network/libbitcoin-network/test/protocols/protocol.cpp:183:12: error: reference to 'session' is ambiguous
  183 |   : public session
      |            ^
/Applications/Xcode_16.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/proc.h:86:8: note: candidate found by name lookup is 'session'
   86 | struct session;

Workaround: a812ef2