JFROG CLI requires different service connection than other jfrog tasks

[aroellig]

Is your feature request related to a problem? Please describe.
To use the jfrog cli in azure builds it requires a different service connections to call the jfrog cli vs calling other tasks like jfrog maven. The jfrog cli requires the myjfrog service connection not the artifactory one. This makes it harder to use in azure builds as a user has to call the jfrog cli then use its commands and then save its outputs somewhere to use them in another task such as jfrog maven

Describe the solution you'd like to see
To be able to use the jfrog cli directly in tasks such as jfrog maven and not have to call it as its own service connection

Describe alternatives you've considered
using the jfrog cli as its own tasks and then saving its outputs so that they can then be used by other tasks