Restricted ZMQ RPC bypasses HTTP restricted-mode resource checks

Summary

monerod --restricted-zmq-rpc does not enforce the same request restrictions as restricted HTTP RPC.

Restricted ZMQ relies primarily on a small method blocklist, so several allowed methods can still accept requests that restricted HTTP explicitly rejects or caps. Confirmed examples include get_output_histogram and get_output_keys.

This can allow externally exposed restricted ZMQ endpoints to bypass intended resource limits, leading to availability issues.

Resolved in https://github.com/monero-project/monero/pull/10424 and v0.18.5.0.