Release v1.16.0

[armanbilge]

To unblock https://github.com/scalameta/munit/pull/477 and Discipline Native/3 which should get us to Cats Native/3.

[armanbilge]

There, I wrote the release notes. You know I'm desperate cause there was no GH magic to help me 😂

---

Scalacheck 1.16.0 is binary compatible with the 1.15.x and 1.14.x series. It is published for Scala 2.12, 2.13, and 3.1+ with Scala.js 1.8+ and Scala Native 0.4. This release is the first to support Scala 3 on the Native platform.

## User-facing PRs
- Adds Discord badge by @paualarco in https://github.com/typelevel/scalacheck/pull/814
- ScalaCheck follows semver since 1.14.x by @larsrh in https://github.com/typelevel/scalacheck/pull/793
- Improve docs for Arbitrary by @ashawley in https://github.com/typelevel/scalacheck/pull/806
- Update examples to 3.0 by @ashawley in https://github.com/typelevel/scalacheck/pull/813
- Add badge to README showing supported versions of Scala by @rtyley in https://github.com/typelevel/scalacheck/pull/819
- Fix `Arbitrary[Year]` instance max value by @dantb in https://github.com/typelevel/scalacheck/pull/825
- Check roundtrip in serialize tests by @ashawley in https://github.com/typelevel/scalacheck/pull/829
- Fix `Arbitrary[Char]` generates 0xFFFE (not a character in Unicode) by @kadzuya in https://github.com/typelevel/scalacheck/pull/835
- Ensure preconditions are satisified when shrinking Commands actions by @jonaskoelker in https://github.com/typelevel/scalacheck/pull/739
- Support `java.time` arbitraries on Scala.js & Native by @armanbilge in https://github.com/typelevel/scalacheck/pull/830
- Enable published snapshots by @armanbilge in https://github.com/typelevel/scalacheck/pull/877
- Onwards and upwards by @armanbilge in https://github.com/typelevel/scalacheck/pull/879

Thank you all!

**Full Changelog**: https://github.com/typelevel/scalacheck/compare/1.15.4...v1.16.0

[rossabaker]

I will cut this tomorrow if nobody tells me to wait.

[rossabaker]

Sorry, another bikeshed: is the plugin prepared for tags that don't begin with v? Alternatively, is there any reason we shouldn't switch to the common Typelevel convention now?

[armanbilge]

Ah, good question. All tags from this point should start with v. MiMa needed some manual intervention to recognize the old artifacts but that's for the better because PVP and stuff. https://github.com/typelevel/scalacheck/blob/0ac8005753ab98b6494fd631502201b97a103638/build.sbt#L56-L68

[rossabaker]

Tagged, but I won't be awake to see the outcome.

[rossabaker]

Oh, we should also update the CHANGELOG. I'll try to remember to do that if it hasn't appeared overnight.