Roll a release (1.1.4)

[SethTisue]

It's been a long time.

[SethTisue]

auto-generated release notes (in gist so as not to make noise on every merged PR) https://gist.github.com/SethTisue/2a62ff234e94163b7e25916246202968

[SethTisue]

it seems that #778 is the only substantive change, but let's of course do this anyway

this is the first release since we moved orgs on GitHub (from lightbend to lightbend-labs), so if publishing fails maybe that will be why, somehow. we'll see

[SethTisue]

(steps from RELEASING.md)

• Check CI passes against the latest Scala versions.
• Draft a new release for the release, allowing GitHub to generate draft release notes automatically.
• Run git tag -a -s 1.x.y -m 'Version 1.x.y'. The name of the tag should NOT have a v prefix.
• In sbt run reload and show version to verify the version.
• In sbt run clean, particularly if you've recently bumped scalaVersion.
• In sbt run publishSigned. You should start seeing "published mima-.. to https://oss.sonatype.org/service/local/staging/deploy/maven2/..".
• In sbt run ++2.13 coreJVM/publishSigned coreNative/publishSigned
• In sbt run ++3.3 coreJVM/publishSigned coreNative/publishSigned
• Find and close your staging repository. (See Sonatype's Releasing the Deployment guide.)
• Switch to a branch (e.g. git checkout -b release-1.x.y)
• In project/plugins.sbt update sbt-mima-plugin.
• In project/MimaSettings.scala update mimaPreviousVersion & clear out mimaBinaryIssueFilters.
• In sbt run testStaging WITHOUT reloading first (testStaging adds the staging resolvers & runs reload).
• Run git commit -am 'Update sbt-mima-plugin to 1.x.y' and PR it (gh pr create or hub pull-request). The PR won't pass CI until the release is available on Maven Central. You may poll repo1 directly (note the trailing slash in the URL).
• Find and release your staging repository.
• Switch back to the main branch and run git push --follow-tags to push the tag.
• Find and merge your update PR.
• Find and hit "Publish Release" on the draft GitHub release.