Drop support of 2.0.x version

Problem/Motivation

Maintaining multiple major versions of a module simultaneously is difficult and time-consuming. Supporting both 2.0.x and newer versions (such as 2.1.x or future releases) complicates development, testing, and security maintenance. To streamline development and ensure a focused support strategy, we propose dropping support for the 2.0.x version once the 2.1.x version is released and there is some level of adoption. Users are encouraged to upgrade to the latest available version to benefit from ongoing improvements.

This approach allows us to concentrate efforts on maintaining a single active version, ensuring regular security releases, bug fixes, and new features for the supported branch, while keeping older versions available for reference but without ongoing maintenance.

Steps to reproduce

N/A

Proposed resolution

- Officially drop active support for the 2.0.x version, meaning no further security releases, bug fixes, or new features will be provided for this version.
- Update documentation and release notes to inform users about the discontinuation of support for 2.0.x.
- Provide clear guidance on upgrading from 2.0.x to the latest supported version, including any potential pitfalls or important changes they need to be aware of during the transition.
- Encourage the community to migrate their installations to the latest supported branch to take advantage of ongoing improvements and security updates.

Remaining tasks

- Draft and finalize documentation for the upgrade path from 2.0.x to the latest version.
- Announce the change to users via appropriate channels (forum posts, release notes, etc.).
- Update module landing pages and repositories to reflect the drop in active support for 2.0.x.
- Monitor and address any issues raised by users during the transition period.

User interface changes

N/A

API changes

N/A

Data model changes

N/A