[Release] 1.16.0 - Githubissues

Build a new Release

Release version: 1.16.0 Release date: 2023-03-17

[x] inform the maintainers of other teams about the release
- use the Slack workflow /new-release in the channel #ask-dmn-feel
[x] schedule a release date
[x] before building the release, inform the maintainers of other teams about the code freeze
[x] build the release using the CI job:
- minor release: https://ci.cambpm.camunda.cloud/view/Sideprojects/job/camunda-github-org/job/feel-scala/job/master
- patch release: use the CI job of the maintenance branch (e.g. https://ci.cambpm.camunda.cloud/view/Sideprojects/job/camunda-github-org/job/feel-scala/job/1.14/)
[x] deploy to Maven Central by releasing the staging repository: https://oss.sonatype.org/#stagingRepositories
[x] create a release in GitHub for the tag: https://github.com/camunda/feel-scala/releases
- attach the artifacts from JFrog: https://camunda.jfrog.io/ui/packages/gav:%2F%2Forg.camunda.feel:feel-engine?name=feel-engine&type=packages
- generate a changelog using GitHub release notes and format it properly
[x] if major/minor release, append the changelog in the documentation for the released version and mention the new features
[x] if major/minor release, archive the documentation of the previous version
- use npm run docusaurus docs:version 1.x in /docs to copy the existing docs under the released version (1.x = the released version)
- update the versions in the configuration /docs/docusaurus.config.js
- set the latest version in docs > lastVersion
- set the current version in docs > versions > current > label
- set the supported versions in docs > versions (enable/disable the "unmaintained version" banner)
[x] update the version that is used by the FEEL REPL script /feel-repl.sc under import $ivy.org.camunda.feel:feel-engine:1.x.y
[x] inform the maintainers of other teams about the successful release :tada:

camunda / feel-scala

[Release] 1.16.0 #610