Purpose

• Improve ease of reading changelog with many adjustments

Rationale

This is more of an aesthetic component to make the changelog easier to read. When run an alphabetical sort on the different changes then it automatically will group like values together. This is very helpful when people use pre-defined or common scope values which consolidates those updates. Conversely if you have a mixture of scoped and non-scoped commits, it will lay out all the non-scoped commits first (which generally mean they cover a larger subset of the project) before the smaller more specific changes are listed.

How did you test?

Adjusted the fake release history fixtures to provide a non-alphabetical ordering to commits and then force it to comply with the resulting test that is in a set order. This ensures the commits were in fact sorted first by scope and secondly by alphabetical descriptions

How to Verify

1. Checkout this pr
2. Reset by 2 commits to remove the fix
3. Run pytest to see the failures where the commits are not in alphabetical order or in scoped order
4. Fast forward merge to the latest commit of this pr
5. Run pytest again to see it is fixed.