Fix detection of TAE data in MDF writing

For some reason recent real data has an ODIN TriggerType of TimingTrigger even if it is not actually TAE data (the other TAE bits such as window/index and central are zero). With the current check, this caues the MDFWriter to output TAE frames when the ODIN bank has that trigger type.

With this change, an event is considered to be TAE only when the TAE window/index is nonzero.

(In general we should not be using TriggerType since it is an enum: an event can only have one type even if it was triggered for two reasons)

/cc @sstahl