Update changelog for 3.0 release

[calebmshafer]

During 3.0 we started adding all of the changes in whatever order happened to be the easiest. In this PR, re-organize and update the docs to portray all of the changes made in a more consumable way.

The layout going for in the PR is;

1. Quick intro to the high level goals of 3.0
2. Transition Guide
   1. Highlight the new codemod tool as a way to get started. Then point to the Breaking Changes list of the 4 point
3. New features added
   • Group by set of functionality to make more consumable
4. Breaking changes organized by group of functionality
5. Renaming tables
   • These should all be covered by the codemod so not as important as everything else in the docs.

[calebmshafer]

@pmconne pushed up what I've done so far. I have some other changes to call out all of the authorization changes but I'll push that soon.

[williamkbentley]

## Remove ninezone-test-app appears on lines 1032 and 1118

[grigasp]

While looking for new stuff that we added for 3.0 I scanned through the changelog JSONs. I'm not sure how often consumers look at them, but it seems they need to be cleaned up as well. IMO they should only mention stuff that's relevant for a person consuming the package, but some of them contain completely irrelevant messages.

For example one of the messages for presentation-backend is: "remove requestContext argument from importSchemas". That has absolutely no meaning to someone using presentation-backend package.

Should we clean them up in this PR?

[calebmshafer]

While looking for new stuff that we added for 3.0 I scanned through the changelog JSONs. I'm not sure how often consumers look at them, but it seems they need to be cleaned up as well. IMO they should only mention stuff that's relevant for a person consuming the package, but some of them contain completely irrelevant messages.

For example one of the messages for presentation-backend is: "remove requestContext argument from importSchemas". That has absolutely no meaning to someone using presentation-backend package.

Should we clean them up in this PR?

@grigasp sure, you can make that update within this PR. I think everyone should take a pass at these since I suspect most people will find messages that are not helpful to users.

[pmconne]

@calebmshafer I thought @scsewall intended the changelogs to be reviewed and sanitized for every release (major, minor, patch) - are we not doing that?
Far too many people simply duplicate their non-user-friendly and/or uninteresting commit messages when doing rush change.

[calebmshafer]

@calebmshafer I thought @scsewall intended the changelogs to be reviewed and sanitized for every release (major, minor, patch) - are we not doing that?
Far too many people simply duplicate their non-user-friendly and/or uninteresting commit messages when doing rush change.

@pmconne we started getting pretty lazy with it last year but definitely need to go back to doing it.

[pmconne]

@pmconne we started getting pretty lazy with it last year but definitely need to go back to doing it.

Is there a process? Can we edit the compiled changelog files? Inspecting and hand-editing each individual changelog JSON file sounds daunting to say the least...

[pmconne]

My preference would be to merge this now and worry about package changelogs in a separate PR.

[calebmshafer]

My preference would be to merge this now and worry about package changelogs in a separate PR.

That's fine by me. It will probably take a few PRs to check them all anyway.

[calebmshafer]

@grigasp, @pmconne, also FWIW, @skirby1996 is currently going through the awful process of back porting a large set of the patch version changelogs to master to make sure they're up-to-date. So don't try and update anything prior to 3.0 yet.