build: Improve release build & process instructions

[emostov]

Changes:

• This makes sure we only ship the JS target by adding the "files" key in package.json with just the build folder. There was some regression in bundling where the distribution went from ~9mb => ~90mb. This brings it back down to ~9mb.
• Update yarn deploy to reflect that we do not automate changelong generation and prevent the footgun of forgetting to build right before publishing.
• Update README instructions

[TarikGul]

How do some of the suggestions at the bottom of PR #529 which is mentioned in issue #534 sound to you? @emostov

[TarikGul]

LGTM Per my comment above i added a bunch of the suggestion's from that previous PR that were put after we merged.

There is one more suggestion to change the version's to vMM-mm-pp. I think it is a good addition but then could also be confusing.

closes: #534

[emostov]

There is one more suggestion to change the version's to vMM-mm-pp. I think it is a good addition but then could also be confusing.

Can you expand on that? We already follow semver, so is the suggestion to used - instead of . somewhere?

[TarikGul]

Yea ofcourse, the suggestion was to replace the use of v5.0.1 as an example and replace it with vMM-mm-pp.

Sorry the was confusing. Basically just replacing our numbers in all the examples above, and replace them with the semver letters.

[niklasad1]

LGTM, I think it was an excellent battle test of the README, letting me doing the previous release.

Maybe increased bundle size was the reason that the 2FA complained (timeout) ^^