THRIFT-6126: Handle unknown Compact and JSON types

[kpumuk]

Ruby Compact and JSON protocol implementations currently allow unknown field and container type identifiers to escape as generic runtime exceptions. In SimpleServer, those exceptions can leave the per-connection protocol error path and stop the accept loop, preventing a later valid client from being processed.

This change reports unknown Compact and JSON types as ProtocolException::INVALID_DATA. The native and pure-Ruby Compact implementations now expose matching exception metadata and preserve the original invalid writer type in diagnostics. SimpleServer can therefore close only the malformed connection and continue accepting clients.

The fuzz harness now relies on these typed exceptions and drops obsolete message matching for invalid types, union validation, negative container sizes, and JSON encoding failures.

• Did you create an Apache Jira ticket? THRIFT-6126
• If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
• Did you squash your changes to a single commit? (not required, but preferred)
• Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
• If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.