Add command to create a release group release

[JeffreyHuynh1]

Overview

The CLI should offer a way to create release group release from the command line

Acceptance criteria

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

Testing plan

example .fossa.yml:

releaseGroup:
  title: example-title
  release: example-release-title
  releaseGroupProjects:
    - projectLocator: custom+1/git@github.com/example
      projectRevision: 12345 
      projectBranch: main

Create a release group release:

• fossa release-group create-release --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-release -c /path/to/.fossa.yml/

Risks

Metrics

References

• ANE-1628

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]

I'd like to see a more thorough test plan, though. The test plan only tests with one project being added to the release group and does not test any of the failure cases. I.e. it would be good to test what happens if you try to create a release group while missing the --project-branch flag. It would also be good to specifically test with multiple projects being added.

• There's a test to see if the release group exists before creating the release: https://github.com/fossas/fossa-cli/pull/1409/files#diff-a6883bdfe80cf7750f86281dce66c203f54d3086a7bce60cb2fe46fb7a5c4019R45

• It seems like you're suggesting that we incorporate more tests at the parsing level when constructing the CreateRelease config. Would it be something similar to: https://github.com/fossas/fossa-cli/blob/master/test/App/Fossa/Config/ReleaseGroup/CreateSpec.hs

  • Or are you suggesting a more detailed manual testing plan?

We should also test the delete command that was added in this PR

The delete command was added in prior a PR. We have tests for it here: https://github.com/fossas/fossa-cli/blob/master/test/App/Fossa/ReleaseGroup/DeleteSpec.hs

[spatten]

  * Or are you suggesting a more detailed manual testing plan?

I was suggesting a more detailed manual testing plan. Sorry for the confusion :)