Server configuration improvements

[RobiNino]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• I used npm run format for formatting the code before submitting the pull request.

---

Note:

• The internal setup-jfrog-cli-server server ID will no longer be available. Set a custom server ID if you need to reference the server directly.

New Feature:

• Support custom server ID

Improvements:

• Unique default server ID for each run of a workflow
• Support multiple configurations

Bug fix:

• Only remove server IDs configured in the specific workflow (should fix Getting --url option is mandatory error for ping and upload commands #94 (comment))

[sverdlov93]

Unique default server ID for each run of a workflow

breaking change? if someone used the old one?

[RobiNino]

The pervious server ID was never documented, using it directly was as using an internal code. I can add the breaking change label if you think it necessary but I'm not sure this actually counts as one.

[sverdlov93]

The pervious server ID was never documented, using it directly was as using an internal code. I can add the breaking change label if you think it necessary but I'm not sure this actually counts as one.

https://github.com/search?q=%22setup-jfrog-cli-server%22+language%3AYAML&type=code&l=YAML

[JackCoplandGranta]

The readme does explicitly mentions this server id (and is now presumably incorrect?):

[tgharold]

As a user, we consider this to be a breaking change and our workflows are failing because of it. We'd have been okay if you had provided a migration path (add the new input in 4.5, then remove the current default in 5.0).

[hazeltonl]

As a user, we consider this to be a breaking change and our workflows are failing because of it. We'd have been okay if you had provided a migration path (add the new input in 4.5, then remove the current default in 5.0).

This may be a good opportunity to look at my Pull Request? It would potentially address this scenario where users inherit breaking changes when only the minor version has been updated. I assume only JFrog employee are able to add reviewers to PRs @RobiNino @eyalbe4
#228

[aairey]

Unique default server ID for each run of a workflow

breaking change? if someone used the old one?

BREAKING CHANGE indeed
Workflows started failing here.

[RobiNino]

Hi all,
We sincerely apologize for the inconvenience caused by this error on our part.
We have just released extension version v4.5.1, which restores the default server ID while also providing the option to set a custom server ID.
Thank you for your understanding and patience.