Support events in AVRO and other formats by supporting jackson-dataformat-binary

## What is your idea?
Support pattern matching on AVRO events. AVRO support is a reasonable next step because:
1. It has wide adoption in streaming systems like Pulsar and Kafka. Any streaming system could use not only the performance characteristics of ruler (which are much needed) but also the semantics of pattern matching.
2. Would serve as a good reference example/stepping stone implementation for other binary formats (or any events with formal schema for that matter).

## Would you be willing to make the change?
Maybe

## Additional context

* Message/streaming systems are lacking a killer pattern/expression/filter language - it could use a de facto "ruler pattern" language, just like SQL is for DBs.

* User who choose to define schemas for their events, expect all interactions to respect schema. Having pattern matching respect data types and fields as defined by the "active or a previous" schema seems like a natural fit for those use cases.

The issue names no files, tests, or entry points. Start by tracing the repository’s event parsing and pattern-matching paths, then establish the intended AVRO scope and acceptance cases; done means AVRO events are supported without violating schema-defined types and fields.

Written by the indexing model from the issue text.