Deprecate builtin addons (links and actions) - no longer included by default

[shilman]

Issue: #1017

What I did

Added HISTORY.md to track changes with each release, modeled after
Meteor’s: https://github.com/meteor/meteor/blob/devel/History.md

How to test

Follow instructions in HISTORY.md (if you want)

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@f5bf4dd). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1038   +/-   ##
=========================================
  Coverage          ?   12.51%           
=========================================
  Files             ?      196           
  Lines             ?     4458           
  Branches          ?      713           
=========================================
  Hits              ?      558           
  Misses            ?     3269           
  Partials          ?      631

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f5bf4dd...598fd65. Read the comment docs.

[usulpro]

I wonder can we additionally add a deprecating warning to @kadira/storybook-addon-... packages?

[shilman]

@usulpro I'm not sure I understand your comment. I just deprecated the builtin-ness of the addons, not the addons themselves, so I don't think it's appropriate to deprecate them. What do you think?

[ndelangen]

I think @shilman means we can deprecate all @kadira/* packages on npm.
We'd need to get membership on those packages, in order to publish.

[ndelangen]

I think a before and after code example would make this text a lot more understandable.

[shilman]

OK I understand @usulpro 's @kadira/* deprecation comment now. Thanks!

[shilman]

@ndelangen Added before/after example. Not sure whether this is the best place for it or format. Suggestions welcome!

[usulpro]

LGTM