Raw banks that cannot be unpacked downstream - how to isolate these online?

• There is a number of ways the processing at the pit is creating raw banks which cannot be unpacked downstream
  • Cannot know about these currently online
• Samples of the errors/warnings found when Sprucing from lhcb-dpa/prod-requests#86 (closed)

Unpack_Hlt2__Event_HLT2_Rec_Trac... WARNING Attempted out-of-range access to packed LHCbIDs. This is bad, do not ignore !
TUnixSystem::DispatchSignals          FATAL segmentation violation

Unpack_Hlt2__Event_HLT2_Rec_Trac...   FATAL  Standard std::exception is caught 
Unpack_Hlt2__Event_HLT2_Rec_Trac...   ERROR vector::reserve
HLTControlFlowMgr                     FATAL Event failed in Node TrackUnpacker/Unpack_Hlt2__Event_HLT2_Rec_Track_Velo

• Need a way to isolate these online and investigate at the pit
  • Run a test unpacking of the raw banks during Hlt2 and stream off events to error stream?
• Largely issues seem to be with track unpacking which can lead to seg faults.
  • Can we turn these into a handled single event error?

@msaur @jonrob @graven @cburr @mfontana @decianm