Add support for What's New and for item discovery by reclassifying tickets

The change in how we handled tickets this release has resulted in lots of "administrative" that are not helpful for showing the history or lineage of changes. To solve this, we will sort tickets that represent data model, sample data, or guidance impacts as "Stories" and those that don't as "Tasks"

Any tickets that:

• are community submitted
• have analysis posted on them
• have meaningful discussion of why a change was made
• are about providing new documentation or guidance

Should be classified as "Stories"

For example, this ticket should NOT be classified as a Story.