feat(types): Add a ValueCodec for Uint complex type

[hoangdv2429]

Description

Closes: #23780
Backport

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[aljo242]

Looks like these were untested - we should test if possible

[hoangdv2429]

Looks like these were untested - we should test if possible

I think we do have tests in codec_test.go ..?

[aljo242]

But it doesnt look like this new type is tested right?

[hoangdv2429]

But it doesnt look like this new type is tested right?

codec_test.go already tested Encode, Decode, EncodeJSON, DecodeJSON and do empty check for Stringify and ValueType. I added the other 2 testcases for exact value.