Add bytes support for 1 length prefix

[JohnChangUK]

Summary

Adds support for hex:"bytes" struct tags for fields that require uint8 (1-byte) length prefix encoding, complementing the existing hex:"bytes16" support for uint16 (2-byte) length prefix encoding.

The Daml compiler erases type synonyms. When you define a field as BytesHex in Daml, the compiler expands it to its underlying type (Text) in the compiled Daml-LF output. By the time go-daml parses the .dalf files, all it sees is:

signerAddress: Text
operationData: Text
root: Text

There's no way to distinguish which Text fields were originally BytesHex and require special encoding. The hardcoded maps (BytesFieldNames, BytesHexFieldNames) work around this limitation by explicitly listing field names that need hex encoding tags.

[github-actions]

👋 JohnChangUK, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[RodrigoAD]

Isn't this very domain (CCIP/MCMS) specific? I see we also have another specific type Uint32ListFieldNames. I feel this shouldn't belong to this lib