[Advanced]: Implement Fuzz Testing

### 🧠 Advanced Contributors

This issue is intended for contributors who are already very familiar with the
[Hiero Enterprise Java](https://hiero.org) codebase and its architectural patterns.

You should feel comfortable:
- navigating multiple modules across `base/, spring/, and mircroprofile/`
- understanding and modifying core library abstractions
- reasoning about API design and backwards compatibility
- updating or extending tests, examples, and documentation as needed
- making changes that may affect public-facing behavior

New developers should start with
**Good First Issues** or **Intermediate Issues** first.

### 🐞 Problem Description

The library may benefit from fuzzing - which is pushing random data to the library in order to identify bugs

We need to research if any fuzzing programs could be relevant and useful to Enterprise Java, then implement it

### 💡 Proposed / Expected Solution

Research and decide if we should implement a small amount of fuzzing for Enterprise Java

### 🧠 Implementation & Design Notes

Read
https://github.com/ossf/scorecard/blob/4eda2f56f70fa619b8785a63deb68aac8e3538ff/docs/checks.md#fuzzing

find suitable language fuzzing options
consider if it will generate useful data for the library and how to ensure it is compatible

test the results of the fuzzing to see if the results are insightful

### ✅ Acceptance Criteria

To merge this issue, the pull request must:

- [ ] Fully address the problem and design goals described above
- [ ] Maintain backwards compatibility unless explicitly approved otherwise
- [ ] Follow existing architectural and coding conventions
- [ ] Include comprehensive tests covering new and existing behavior
- [ ] Update relevant examples and documentation
- [ ] Pass all CI checks
- [ ] Include a valid changelog entry
- [ ] be a DCO and GPG key signed as `git commit -S -s -m "chore: my change"` with a GPG key set up

### 📚 Additional Context, Links, or Prior Art

Optional.