Include Spider X Blocks on/off events in the AFF data feed

Problem:

The AFF (Aircraft Flight Following) data feed carries engine and takeoff/landing events from the Spider X digital flight log, but not blocks on/off events, so systems consuming the feed can't derive block times from it.

Desired outcome:

Consumers of the AFF feed want the full set of digital flight-log events — including blocks on/off — so they can calculate block time without a separate data source.

Proposed change:

Add the Spider X Blocks On and Blocks Off events to the AFF JSON feed alongside the existing engine and takeoff/landing events.