Replace ApigeeAuthKeyType and ApigeeAuthKeyInput with the Key Apigee module for improved flexibility and maintainability

[mxr576]

Is your feature request related to a problem?

The current integration for managing Apigee credentials within the Apigee Edge module (ApigeeAuthKeyType and ApigeeAuthKeyInput) is tied to project-specific decisions made over 7+ years ago. These implementations have become outdated, and a more flexible, maintainable solution is needed.

Describe the solution you would like

We propose replacing the existing ApigeeAuthKeyType and ApigeeAuthKeyInput in the Apigee Edge module with the key types and key inputs provided by the Key Apigee module (https://www.drupal.org/project/key_apigee) that Pronovix released after Apigee Summit 2024.

The Key Apigee module integrates with the Drupal Key module and provides a modern, low-level solution for managing Apigee Management API credentials securely and efficiently. It allows for better configurability, maintainability, and future-proofing, without being tied to legacy project-specific decisions.

This replacement should be backward compatible, ensuring a smooth transition for existing users. Any potential discrepancies or issues can likely be addressed through an update hook within Drupal.

Describe alternatives you have considered

An alternative would be updating the existing ApigeeAuthKeyType and ApigeeAuthKeyInput implementations to modernize them. However, using the Key Apigee module offers a more standardized and tested solution that aligns with the broader Drupal ecosystem, making it a more sustainable choice.

Additional context

The current key type and key input implementations within the Apigee Edge module have aged significantly and would benefit from a rewrite. The Key Apigee module already provides a well-designed, flexible solution for securely storing Apigee credentials. Replacing the existing implementation would bring the module up-to-date with modern Drupal practices while maintaining backward compatibility.

Verification of backward compatibility will be necessary, but any required fixes should be manageable via an update hook.