AnalysisTop: Separate calo jet and track jet b-tagging and bloatware reduction

This MR does a few things related to how b-tagging is handled in AnalysisTop

1. Configuration of b-tagging WPs is now possible separately for calo jets and track jets. This is necessary to accommodate different level of support for recommendations for EMPFlow and VR track jets in recent CDI files
2. Do not store MV2 and DL1/DL1r/DL1rmu variables (weight, pb, pc, pu probabilities) unless user has specified a b-tagging WP using the respective algorithm