Contract Reader Handle Empty Bytes

[EasterTheBunny]

In some cases, a contract call will return an empty result 0x, which decodes to an empty set of bytes. The codec can't decode this empty set except in specific cases where a slice of bytes is the expected result.

This commit adds a short-circuit to decoding an empty result where the return value is unaltered.

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

[ilija42]

Can we add a test in TestChainComponents?

[EasterTheBunny]

TestChainComponents

I was thinking about this, but the edge case is simply in implementation and the chain components tests are unaware of the exact bytes returned by the RPC. To top it off, we didn't catch this issue because it wasn't an issue using the simulated chain.

I think I can add a special test harness for this case (both GetLatest and Batch), but I will need to simulate an empty data return at the lowest level. I'll look at what kind of lift that will take. Maybe there is a shortcut.