Declare Drupal 11 compatibility

Looks good. +1 for RTBC

Why was Drupal 9 support removed?

Because it is unsafe to use it as it has been unsupported since November 1, 2023.
But in case of some reason you still need to use this project on a Drupal 9 setup, there is a way to use it by combining a patch to the info file and the use of drupal-lenient composer plugin https://www.drupal.org/docs/develop/using-composer/using-the-drupal-leni... →

Need to restore Drupal 9 support.

Problem/Motivation
When installing the module with Composer using:

composer require drupal/change_pwd_page:^2.0

Composer fetches the official tarball release (e.g. 2.0.0) from Drupal.org.
This release is created only when a tag is added, so it does not include the latest commits in the 2.0.x branch.

As a result, the code installed via Composer can be outdated compared to the current 2.0.x branch.

Steps to reproduce

Run composer require drupal/change_pwd_page:^2.0.

Check the code – it is locked to the 2.0.0 tag.

Run git clone --branch 2.0.x https://git.drupalcode.org/project/change_pwd_page.git.

Compare the code – the cloned branch contains the latest commits that are not in the 2.0.0 release.

Expected result
Composer installation should provide access to the latest code from the 2.0.x branch (e.g. using 2.0.x-dev), not only the last tagged release.

Actual result
Composer installs the outdated 2.0.0 release, missing recent commits from 2.0.x.