RPC: detect attempts to enable it when compiled out?
When RPC is cargo-configured out, the rpc
field in the configuration simply vanishes (after !2009 (merged)). The effect will be an "unused config key" warning.
We should decide if this is the right behaviour. Another option would be to reject such configs (eg as we do for bridges.)
My initial feeling is that a warning is the right balance of salience.