Investigate impact of jcenter shutdown on Fuse Tooling

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

there are traces in log of Fuse Tooling test. it seems to be used through Camel Catzalog, grape -> Ivy dependency chain.

impact:

• 1st may 2021: in theory no impact but several services are shutdowned and not sure how to test it
• 1st February 2022: if not migrated: in best case, long timeout that will slow down most actions. in worst cases, broken features/freezes

when the Bintray JCenter will be decommisioned, a possible workaround for software that has not been migrated:

• Customize Ivy settings used by Grape http://docs.groovy-lang.org/latest/html/documentation/grape.html#Grape-CustomizeIvysettings
• use a ~/.groovy/grapeConfig.xml which doesn't contain bintray entries

Identified actions in Fuse Tooling:

• Upgrade Camel to a version using a fixed version of groovy in Camel Language Server [FUSETOOLS2-1030]
• Upgrade groovy lib in /org.fusesource.ide.camel.model.service.impl to 2.5.x with fixed groovy FUSETOOLS-3462