This change handle the case when cron:remove can not be executed properly, for example when setup:upgrade or Magento 2 installation wasn't done properly.
Try/Catch prevents breaking of deployment (as cron stopping is nice to have, but not required).
I believe stopping cron jobs while deploying is a good practice
The path to bin/magento in the crontab will contain the release number while executing cron:install manually, so this path should be updated by the deployment process
This change handle the case when cron:remove can not be executed properly, for example when setup:upgrade or Magento 2 installation wasn't done properly.
Try/Catch prevents breaking of deployment (as cron stopping is nice to have, but not required).