add delete evidence by subject endpoint call

[mnsboev]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.

---

Description:
This PR is the part of the two PRs which introduce a new command for the jf evd CLI tool that allows users to delete evidence based on specific criteria. The new delete command resolves the subject and facilitates the deletion of evidence using its name.

jfrog-cli-artifactory PR: jfrog/jfrog-cli-artifactory#123

The command uses the same subject definition as create and verify commands.
The output of help command:

Name:
  jf evd delete-evidence -  Delete evidence associated with a specified subject by evidence name. 

Usage:
  jf evd delete-evidence [command options] --evidence-name=<value>
  
Options:
  --access-token              [Optional] JFrog access token.
  --build-name                [Optional] Build name.
  --build-number              [Optional] Build number.
  --evidence-name             [Mandatory] Evidence file name.
  --package-name              [Optional] Package name.
  --package-repo-name         [Optional] Package repository Name.
  --package-version           [Optional] Package version.
  --project                   [Optional] Project key associated with the created evidence.
  --release-bundle            [Optional] Release Bundle name.
  --release-bundle-version    [Optional] Release Bundle version.
  --server-id                 [Optional] Server ID configured using the config command.
  --subject-repo-path         [Optional] Full path to some subject location.
  --url                       [Optional] JFrog Platform URL.
  --user                      [Optional] JFrog username

Example of call:
jf evd delete --release-bundle mishas_bundle --release-bundle-version 45 --evidence-name release-bundle-signature-1753360796034-204c2ab4.json

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

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

---

13 out of 14 committers have signed the CLA.
✅ (omerzi)[https://github.com/omerzi]
✅ (eyalbe4)[https://github.com/eyalbe4]
✅ (sverdlov93)[https://github.com/sverdlov93]
✅ (talarian1)[https://github.com/talarian1]
✅ (yahavi)[https://github.com/yahavi]
✅ (RobiNino)[https://github.com/RobiNino]
✅ (attiasas)[https://github.com/attiasas]
✅ (EyalDelarea)[https://github.com/EyalDelarea]
✅ (eranturgeman)[https://github.com/eranturgeman]
✅ (eyalb4doc)[https://github.com/eyalb4doc]
✅ (bhanurp)[https://github.com/bhanurp]
✅ (ehl-jf)[https://github.com/ehl-jf]
✅ (BlasttS)[https://github.com/BlasttS]
❌ @remib
remib seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}