[FEATURE] Revise methods for mass deletion and button locations

[mattdawkins]

Deleting the detentions shown is not the way I would really handle this and leads to confusion when considering thresholds

[subdavis]

Please provide more details. How should this change?

[mattdawkins]

Usually I think it's the reverse, users might want to delete everything not showing because they've set some threshold they like? Not the other way around.

Also (this might be debatable) but it's confusing that the delete button is so close to the tracks list, some users might think that when they highlight a detection that these buttons perform standard deletion on the single detection and accidentally delete everything. I did this once.

[waxlamp]

@mattdawkins, I still need some context and information on this. What's the specific thing you think is wrong, and what would you like to see replace it or be added alongside it?

[subdavis]

This can probably be rolled into some kind of "UX improvement for annotation viewer" thing. I agree with Matt that the button design isn't ideal, but it's not clear how to improve it yet. Needs discussion.