Support `ProtocolConfig` (v0.17)

In v0.17, fee asset ID is factored out into [`ProtocolConfig`](https://github.com/0xMiden/protocol/blob/528a500b0cb9ccf85091947131a60b722db846f9/crates/miden-protocol/src/protocol_config/mod.rs#L37), who's commitment is instead part of the block header.

Clients now need a way to get this configuration, at the very least to access the fee asset ID that they could previously get from the header.

Support therefore includes:

1. Storing this config
2. Verifying the commitment
3. Exposing this config via RPC

We are expecting this config to change _very_ rarely - on the order of months. (1) therefore makes sense to keep this in a separate table which can be looked up via commitment.

For (3) we need a new endpoint. The values can be heavily cached since they change so rarely, and are therefore valid for large block ranges. I imagine query by commitment makes the most sense.