penumbra(rpc): restore chain id checks in query services

[erwanor]

We promoted chain_id to a top-level AppParameter datum, but various component need it to perform chain id checks in their query service, in order to fast-reject requests that target a different instantiation of the penumbra network (e.g. preview vs. testnet). This is a reminder to circle back on this later, for now I'm removing them.

Originally posted by @erwanor in #3617 (comment)

[hdevalence]

I am wondering if we would be better off removing all of those fields entirely, and using a custom header for this purpose. Then the checking/insertion could be handled via middleware.

[erwanor]

I wasn't sure if there was appetite to do that, but I completely agree and this also short circuits data remodeling work we would have to do on the application front.

[erwanor]

IMO if a check has to be duplicated on every request handler, it's a strong sign that it is in fact, middleware.