MuonReconstruction switch to public ToolHandles to retrieve the AtlasExtrapolator

Hi,

this MR is a trial to reduce the memory footprint of the muon reconstruction code as reported in ATLASRECTS-5648. @goetz found out that the following instances of tools are duplicated throughout the job with the same configuration.

--- Identical instances
  7499 Trk::RungeKuttaPropagator/AtlasRungeKuttaPropagator
  7450 Trk::STEP_Propagator/AtlasSTEP_Propagator
  5525 Trk::Navigator/AtlasNavigator
  5291 Trk::MaterialEffectsUpdator/AtlasMaterialEffectsUpdator
  5291 Trk::MaterialEffectsUpdator/AtlasMaterialEffectsUpdatorLandau
  5208 Trk::Extrapolator/AtlasExtrapolator
  5148 Rec::MuidCaloEnergyParam/MuidCaloEnergyParam
  4435 Trk::ResidualPullCalculator/ResidualPullCalculator
  4102 Trk::RungeKuttaIntersector/RungeKuttaIntersector
  4101 MdtCalibrationDbTool/MdtCalibrationDbTool
  3697 Muon::MuonTrackSummaryHelperTool/MuonTrackSummaryHelperTool
  2574 Rec::MuidCaloEnergyMeas/MuidCaloEnergyMeas
  2573 Rec::MuidTrackIsolation/MuidTrackIsolation
  2279 Trk::Navigator/MuonNavigator
  1994 MdtCalibrationTool/MdtCalibrationTool
  1982 Muon::MuonEDMPrinterTool/MuonEDMPrinterTool
  1842 Muon::MuonClusterOnTrackCreator/MuonClusterOnTrackCreator
  1719 Muon::MdtDriftCircleOnTrackCreator/MdtDriftCircleOnTrackCreator
  1715 Rec::MuidCaloEnergyTool/MuidCaloEnergyToolParam
  1637 Trk::TrackingVolumeDisplayer/TrackingVolumeDisplayer
  1637 Rec::MuidCaloMaterialParam/MuidCaloMaterialParam
  1553 Trk::MultipleScatteringUpdator/AtlasMultipleScatteringUpdator
  1544 SiLorentzAngleTool/SiLorentzAngleTool
  1453 Trk::MaterialEffectsUpdator/MuonMaterialEffectsUpdator
  1125 Trk::STEP_Propagator/MCTBPropagator
  1043 Trk::KalmanUpdator/MuonMeasUpdator
  1019 CscAlignmentTool/CscAlignmentTool
  1010 CalibCscStripFitter/CalibCscStripFitter
  1010 QratCscClusterFitter/QratCscClusterFitter
  1008 CscCalibTool/CscCalibTool
   863 SiLorentzAngleTool/PixelLorentzAngleTool

Given that the AtlasExtrapolator is a fairly big boy in this and game and that it should be quite thread-safe. This MR uses publicTool handles to expel him to the back of the ranking.

Adding: @emoyse, @elmsheus, @goblirsc