[BUG] Multiple Confidence Pairs not sorting and disabling properly

[BryonLewis]

Describe the bug
It looks like tracks with multiple confidence pairs aren't properly grabbing the highest value when displaying and then handling the disabling of that type properly by swapping to the next level.
To Reproduce
Steps to reproduce the behavior:

1. Have a dataset with multiple confidence pairs on a track with one higher than the other. If done in a csv make sure that the higher one is the second value in the list
2. Initially take a look in the attributes editor to see which one is highest and the type that is assigned to the data
3. Turn off the higher confidence pair in the type list
4. Notice that the higher confidence pair is still visible in all of the relevant areas (annotation, event viewer, timeline, track list)

Related data
Is there a dataset on viame.kitware.com that illustrates this bug well? Please link it here.

Expected behavior
First the type should correspond to the highest confidence pair if not filtered by the confidence filter
Second I would assume that if we disable a specific type it should jump down to the next lowest type in the confidence pairs. I.E. if the highest type is turned off the track automatically swaps to the next type? I DONT KNOW IF THIS IS WHAT WE WANT we may want different behavior based on the confidenceFilter instead.

Additional context

[BryonLewis]

Looking into this more all our drawing references rely on the first item in the confidence pair list being the proper type to use for display.
The filtering by toggling off types in , just tell if the type has a confidenceLevel aboce the threshold and a type that is visible - https://github.com/VIAME/VIAME-Web/blob/master/client/src/use/useTrackFilters.ts#L67
So it will render the item with the top type as long as one type is visible and above the confidenceLevel.

Current method of rendering Types:

• In the trackItem we use getType function on the track object itself - https://github.com/VIAME/VIAME-Web/blob/master/client/src/components/TrackList.vue#L132
• Within the annotation layers it looks like we use the same thing to get the current type from the array - https://github.com/VIAME/VIAME-Web/blob/master/client/src/components/LayerManager.vue#L120

Proposal:

1. Create a local variable to each track that stores the current type based. (not part of JSON, just local to the track itself)
2. Allow setting of the current type during the filtering process in useTrackFilters where the current type index is set based on the ConfidenceLevel and the track itself being visible.
3. Make sure there are safeguards in place for when we manually edit the type through the type dropdown list tool for tracks.
4. Also give some consideration to the eventual ConfidenceEditor which will allow for deletion, addition and removal of confidence pairs for a single track.