Do not run changeset linter in Version Packages PRs

[kachkaev]

Continues #579, fixes CI failures in Version Packages PRs.

From docs:

NOTE: status will fail if you are in the middle of running version or publish. If you want to get changeset status at the time of a version increase and publish, you need to run it immediately before running version.

See failed run example for #578

---

Extra: I’ve also bumped @changesets/cli to get this upstream PR in: changesets/changesets#905

Older versions of @changesets/cli use built-in Prettier (v1). It generates lists with alternating * and -, which in turn breaks yarn lint:markdownint. Upstream issues: changesets/changesets#938, prettier/prettier#4369.

[kachkaev]

I moved this command one step up to reduce time gap between repo checkout and branch reference creation

[codecov]

Codecov Report

Merging #586 (0b92842) into main (d3b19a5) will not change coverage.
The diff coverage is n/a.

❗ Current head 0b92842 differs from pull request most recent head 3603ec1. Consider uploading reports for the commit 3603ec1 to get more accurate results

@@           Coverage Diff           @@
##             main     #586   +/-   ##
=======================================
  Coverage   58.06%   58.06%           
=======================================
  Files         263      263           
  Lines        4149     4149           
  Branches      995      995           
=======================================
  Hits         2409     2409           
  Misses       1434     1434           
  Partials      306      306           

Flag	Coverage Δ
site-integration	58.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.