function encodeKeyName behaves incorrectly for dynamic keys when dynamic key part is <bytesN>

[CJ42]

I'm submitting a...

• bug report
• feature request
• question about the decisions made in the repository
• question about how to use this project

Summary

When using the encodeKeyName function with a data key that contains a dynamic key part of type <bytesN>, the hex value generated is incorrect. For bytesN, the padding should occur on the right side ✅ instead of on the left side ❌

See the following screenshots to see the error and reproduce it.

Instead, the encoding should look as follow:

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)