refactor(release:report): Split release report commands

[tylerbutler]

The release report command arguments were confusing, especially after the --all flag was added. This PR refactors the release report command into two separate commands, release report and release history.

• When flub release report is run for a single release group (i.e. flub release report -g azure), the specified release group's version will be loaded from the repo, and its immediate Fluid dependencies will be included in the report. This is useful when we do a client or azure release and we want to include the dependency versions that the release group depends on.
• To run the previous default mode where you interactively choose each release, pass the --interactive flag.
• flub release history replaces flub release report --all. It will output a list of all releases for a single release group when the --releaseGroup flag is passed. The number of releases shown can be limited using the --limit flag.

BREAKING CHANGE: The --all and --limit flags have been removed from flub release report. Use flub release history instead.

---

Note for reviewers:

As implemented, in order to report on a specific version of a release group and follow its dependencies, you must check out the version of the repo at that release. For example, if you want to generate a report of the 1.1.1 client release and its dependencies, you would first check out the release tag: git checkout client_v1.1.1 then run flub release report -g client -o <PATH>.

[CraigMacomber]

PR description mentions "flub release all": did you mean "flub release report all"?

[tylerbutler]

PR description mentions "flub release all": did you mean "flub release report all"?

Yeah -- now it's flub release history.