create detailed summary for every command when JFROG_CLI_COMMAND_SUMMARY_OUTPUT_DIR is set

[ahippler]

• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• The pull request is targeting the dev branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....

---

Some commands use the cliutils.GetDetailedSummary which checks JFROG_CLI_COMMAND_SUMMARY_OUTPUT_DIR but others only use the detailed-summary cli flag. This PR unifies this and uses cliutils.GetDetailedSummary for every command.

This will be useful for the github setup-jfrog-cli action to enable the summary on every command.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[ahippler]

I have read the CLA Document and I hereby sign the CLA

[EyalDelarea]

Hey @ahippler,

Thank you for your contribution!

To add commands to the summary, you would need to record relevant data during the command's execution and implement functions to transform this data into markdown. Unfortunately, achieving this for every command with just a one-liner change isn’t feasible. Moreover, we aim to avoid summarizing every command, as doing so would dilute the purpose of having a concise and meaningful summary.

Could you elaborate on the specific use case you have in mind? I’d love to hear your thoughts!

If you're looking for more information on how to implement new command summaries, feel free to check out the documentation here.

Best regards,
Eyal

[ahippler]

Hi. The PR is not about adding commands to the summary. Its about unifying the usage with the github action setup-jfrog-cli. The action configures the env var JFROG_CLI_COMMAND_SUMMARY_OUTPUT_DIR and some commands generate automatically a summary in the github action run. Other commands like jf go publish do not create an entry in the job summary.

[github-actions]

This pull-request was closed due to 7 days of inactivity after being marked as stale. Feel free to reopen it if it remains relevant.