- and refuses with a sentence instead of letting algod answer with two base32 hashes

- and refuses with a sentence instead of letting algod answer with two base32 hashes

Bumps [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping) from 2.9.19 to 2.11.21.
- [Release notes](https://github.com/web-platform-dx/baseline-browser-mapping/releases)
- [Commits](https://github.com/web-platform-dx/baseline-browser-mapping/compare/v2.9.19...v2.11.21)

---
updated-dependencies:
- dependency-name: baseline-browser-mapping
  dependency-version: 2.11.21
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

PreEncodedBlockCert was msgp:ignore'd and encoded with protocol.EncodeReflect, so the block service and the ws fetcher both built block responses through reflection. Switch its codec.Raw fields to msgp.Raw and generate the codec.

The _struct codec:"" tag keeps both fields unconditional, matching EncodedBlockCert, which is what the fetching side decodes these bytes into. Verified byte-identical to the previous reflection encoding over randomized block and certificate pairs, including the empty-field case.

Note that go-codec does not treat msgp.Raw as verbatim msgpack, so every encoder of this type has to move together; protocol.EncodingTest skips randomized comparison for msgp.Raw for the same reason.

TxService encoded its response with protocol.EncodeReflect while the client side already decodes through the generated txSyncResponse decoder. Encode through the same named type so both ends go through msgp, and have getFilteredTxns return it directly.

The wire format is unchanged: TestRandomizedEncodingtxSyncResponse already requires EncodeMsgp and EncodeReflect to agree byte for byte, and the empty response the serve side actually sends is now pinned in the test.