Set up trigger jet tracking operations with FTF in AthenaMT

This is to make a start with building track moments in the jet trigger. I've done the following:

• Extend the offline jet track moment tool configuration helpers to accept a string specifier that indicates what track/vertex collections should be used (defaults to offline, space to add multiple online/alternative track collections).
• Move FS HLT tracks to the jet domain from the b-jet domain in TriggerEDMRun3
• Add track options to the jet signature dict
• Add an optional tracking sequence that will be scheduled for "_ftf" jet chains, which runs FTF, b-jet vertexing, creates the jet track and track-vertex-association containers, and makes PseudoJets from the tracks
• Schedules jet track moments starting from the FTF tracks
• Added two test chains to the menu.

I didn't yet change anything about the HLT track naming convention because I just reused an existing name, and it appears as though any changes would affect all clients of makeInDetAlgs. So I think we should start to look at this in a separate branch/MR.

To do (dependent on other work):

• Replace b-jet vertexing with something more generic
• Add an FTK case
• Factorise the online/offline code a little more such that the track collection map e.g. is provided by an import from the trigger jet domain

I will investigate whether this is enough to allow setting up an HLT PFlow sequence.

FYI @jbossios, @peter, @doglioni, @boveia, @cantel