Map Events HostErrors to Human-Readable Descriptions

[codeZe-us]

If an error occurs related to emitting events (e.g., exceeding size limits), the host returns a HostError::Events code. Users need to know exactly what constraint was violated.

• Map HostError::Events codes to understandable explanations about event emission failures.
• Add these error descriptions to the error parser.

Expectation: Prism clearly displays why a contract's event emission failed, such as "too many topics" or "data payload too large".

Contributor telegram group: https://t.me/+sII7WPhll2liMGNk

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.