Release group commands

[JeffreyHuynh1]

Overview

The CLI should offer a way to create release groups from the command line. Creating and deleting other org-level objects should be done through their own command.

Acceptance criteria

• There is a way to create and delete a release group from the CLI.

• Emit audit logs on release group creation in CORE

Testing plan

example .fossa.yml:

releaseGroup:
  title: example-title
  release: example-release-title
  releaseGroupProjects:
    - projectId: custom+1/git@github.com/example
      projectRevision:   12345 
      projectBranch: main
  licensePolicy: license-policy-name 
  securityPolicy: security-policy-name
  teams:
      - team1
      - team2

Create a release group:

• fossa release-group create --title example-title --release example-release-title --project-locator custom+1/git@github.com/example --project-revision 12345 --project-branch main
• fossa release-group create -c /path/to/.fossa.yml/

Add projects to a release group:

• fossa release-group add-projects --title example-title --release example-release-title --project-locator custom+1/git@github.com/example --project-revision 12345 --project-branch main
• fossa release-group add-projects -c /path/to/.fossa.yml/

Delete a release group:

• fossa release-group delete --title example-title

Delete a release group release:

• fossa release-group delete-release --title example-title --release example-release-title

Risks

Metrics

References

• CORE PR
• ANE-926

Checklist

• [x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• [x] If this PR introduced a user-visible change, I added documentation into docs/.
• [x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• [x] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
• [x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• [x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

[JeffreyHuynh1]

CORE wanted me to use their existing endpoints for the release group commands. As a result I baked in a lot of logic from the my pr in CORE into this one. There were a lot of additional endpoints added to retrieve policy ids, team ids, and to validate the existence of release existing release groups with the same name.

With the addition of all the endpoints I added, I can see a future where we just tell the user to pass in the release group id and release id for commands such as (add-projects, delete, delete-release). We would do this by creating new subcommands (retrieve-release-groups, retrieve-releases) and with that users would be able to straight up retrieve the id's that they need. For now, I would like to keep the implementation as is as adding these additional commands will require much more work.