Setup

[x] Create a new branch for this release: git checkout -b releasev0.1.17
[x] Update release version in ./docs/whats-new.rst
[x] Increase release version in ./setup.py
[x] Create a PR to prepare it, name it with one of the Nature emoji and make sure it was never used before
[x] Activate RTD build for this branch

Prepare code for release

[x] Check the code for the deprecated decorator and enforce the deprecation policy:
- [x] If code is marked as deprecated since version = v0.1.17 : do nothing (first version with deprecation warning)
- [x] If code is marked as deprecated since version = v0.1.17-1 : do nothing (2nd and last version with deprecation warning)
- [x] If code is marked as deprecated since version = v0.1.17-2 : delete code (code will raise an error)
[x] Update the documentation according to new deprecations

[x] Update CI tests data used by mocked ftp and http servers. Use CLI citests_httpdata_manager
[x] Update list of valid Reference tables with NVS server
[x] Update static assets files
[x] Update the cheatsheet PDF with all new release features

[x] Manually trigger upstream CI tests for the release branch and ensure they are passed
[x] Update pinned dependencies versions in ./ci/requirements/py*-*-pinned.yml environment files using upstream CI tests information
[x] Possibly update ./requirements.txt and ./docs/requirements.txt if the oldest dependencies versions were upgraded
[x] Make sure that all CI tests are passed
[x] Make sure the documentation for the release branch is built on RTD

[x] Last check the ./setup.py file version of the release and that the documentation is ready
[x] "Create a new release" on GitHub. Choose a release tag v0.1.17, fill in the release title and click on the Auto-generate release notes button. Once ready, publish the release. This will trigger the publish Github action that will push the release on Pypi.
[ ] Checkout on Pypi and Conda that the new release is distributed.