Let dependencies be defined using HTTP URLs

[nicolaferraro]

We allow mvn: dependencies with camel: and runtime: wrapper. We should allow users to specify HTTP dependencies on libs (to load custom JAR that are not present in Maven central).

[squakez]

I am not sure if this is still relevant to these days, as the feature was requested already long time ago. If it's still the case, maybe we can think to upload the dependency on the operator local m2 via [install-file] just the first time we use it. Maybe we can generate some SHA in order to guarantee uniqueness starting from the URI that defines the dependency. The only concern I have is if it makes sense for the operator to host some dependency that could be malicious (altough the same could apply for any mvn dependency I guess).

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[squakez]

Managed in #2834

[squakez]

I got confused. Now that we have local file dependency in place, we may turn this easily into a new feature that will leverage that development. Ie, we can let the CLI download the http located jar in a temporary file and reference that file such as -d https://my-repo/my-dependency.jar --> -d file:/tmp/my-dependency.jar.