[pipeline-library/updatecli] Allow custom version and execution in current "pipeline node" context

[dduportal]

This issue tracks a set of useful improvement for the updatecli() pipeline library to ease the Infra team daily tasks:

• We want to test early some updatecli version without having to release a new Packer Image. Allowing to specify a custom updatecli version in the pipeline library would allow this:
  • See specific issue in the pipeline-library repository: feature request: allow running updatecli() with a custom version pipeline-library#908
• We want to allow executing updatecli in the "calling" pipeline's node context. It would allow us simplifying pipeline such as https://github.com/jenkins-infra/kubernetes-management/blob/0d4ffc76660c8cb667a9f7fb3f9f8b94a7fc7bf7/Jenkinsfile_updatecli#L26-L41 or https://github.com/jenkins-infra/jenkins-infra/blob/production/Jenkinsfile_updatecli where we need to run a set of "preliminary" commands before calling updatecli.
  • See specific issue in the pipeline-library repository: feature request: allow running updatecli() in the current agent pipeline-library#518
  • Definiton of done should be both specified pipelines using the new feature