feat: Add lazy filtering support for inlet events by time range, ordering, and limit

[hussein-awala]

This PR extends the asset events API client and inlet events accessor to support additional query options while keeping the accessor lazy, meaning events are only fetched when accessed.

Changes

• Updated InletEventsAccessors.__getitem__ to accept optional filtering arguments (after, before, ascending, limit) without breaking existing usage (new key type is tuple[<existing key type>, dict])
• The accessor continues to lazily fetch events from SUPERVISOR_COMMS only when accessed, but it will only fetch the events that match the filters when they are provided.

Impact

• Existing calls like accessors[asset] continue to work as before.
• New functionality allows lazy, filtered queries by time range, limit, and sort order.
• Enables more efficient and flexible retrieval of asset event history without eager fetching.

Use Cases

• Useful when the asset is used as input and not as a trigger source.
• Easily retrieve the latest available value (ascending=False and limit=1).
• Filter by date range for backfill scenarios without fetching the full history and filtering locally.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[uranusjr]

There are some optimisation to be had (specifically how we calculate _asset_events for verious things, somethings not needed), but I’m happy with the interface and we can just improve incrementally when we feel like doing it.