Drupal 11 ConfigForms fixes as New parameter added to ConfigFormBase::__construct

[kedarkhaire]

Is your feature request related to a problem? Please describe.

As per the Drupal 11 release, the \Drupal\Core\Form\ConfigFormBase::__construct now accepts a $typedConfigManager argument. This argument must be an instance of \Drupal\Core\Config\TypedConfigManagerInterface. It is optional in 10.2 and will be required in 11.0.
To make our module compatible, we have to update all configuration form with the required change.

Link of change record - https://www.drupal.org/comment/reply/3404140

Fixes needed on the following Apigee Admin Configuration Forms (Admin > Configuration > Apigee)

1. AppSettingsForm.php (Apigee > Apps > General)
2. EdgeEntityDisplaySettingsForm.php (Apigee > Apps > Developer Apps > Display Settings)
3. DeveloperAttributesSettingsForm.php (Apigee > Developer > Custom Attributes)
4. ApiProductAccessControlForm.php (Apigee > Api Products > Api Product Access)
5. apigee_edge_debug/src/Form/ConfigForm.php (Apigee > Debug)

Describe the solution you would like

1. Classes extending ConfigFormBase and that do not override the constructor do not need to change anything now nor in the future: they automatically inherit this new behavior.
2. Classes extending ConfigFormBase that do override the constructor will need to update this by Drupal 11.
3. Classes that have a $typedConfigManager property continue to work fine in Drupal 10 thanks to the base class' property not being typehinted, but will need to be updated by Drupal 11.