(docs/fix): track latest release by SemVer

- in case a backport release is added, such as a backport of the
  upcoming v0.1.1

- "latest" in GitHub releases means latest by date, which means
  backports are considered latest by definition
  - using SemVer with the "tag" badge (not release anymore :/)
    more or less resolves this for the README, but GH releases page
    will always show by date :/

- "commits since" is also currently tracking "latest" release by date
  - no fix to this yet, c.f. badges/shields#1955 (comment)
    - manually putting the latest SemVer tag for now :/ :/ :/ :/

README.md

@@ -2,8 +2,8 @@
 
 <!-- releases / versioning -->
 [![package-json](https://img.shields.io/github/package-json/v/agilgur5/mst-persist.svg)](https://npmjs.org/package/mst-persist)
-[![releases](https://img.shields.io/github/release/agilgur5/mst-persist.svg)](https://github.com/agilgur5/mst-persist/releases)
-[![commits](https://img.shields.io/github/commits-since/agilgur5/mst-persist/latest.svg)](https://github.com/agilgur5/mst-persist/commits/master)
+[![releases](https://img.shields.io/github/tag-pre/agilgur5/mst-persist.svg)](https://github.com/agilgur5/mst-persist/releases)
+[![commits](https://img.shields.io/github/commits-since/agilgur5/mst-persist/v0.1.0.svg)](https://github.com/agilgur5/mst-persist/commits/master)
 <br><!-- downloads -->
 [![dt](https://img.shields.io/npm/dt/mst-persist.svg)](https://npmjs.org/package/mst-persist)
 [![dy](https://img.shields.io/npm/dy/mst-persist.svg)](https://npmjs.org/package/mst-persist)