Support for multiple endpoints

Problem/Motivation

Support for multiple Azure CDN Endpoints. It would be beneficial in a headless Drupal project to have support for multiple CDN Endpoints.

Steps to reproduce

In a headless multisite using the Domain Access module and multiple Vue.js frontends or a similar architeture, clearing caches of multiple Azure CDN Endpoints would be a hurdle.

Proposed resolution

It would be useful having the possibility of adding a comma-separated list of CDN endpoints.

Remaining tasks

• Implement the Changes: Modify the Azure CDN Purge module to handle a comma-separated list of CDN endpoints in both the settings and purging logic.
• Testing: Thoroughly test the modified module in a development environment with scenarios involving multiple endpoints.
• Documentation: Update the module's documentation to include the new feature and instructions on how to use it.
• Community Review: Submit the patch to the Drupal community for review and feedback, addressing any concerns or suggestions they might have.

User interface changes

The settings form (AzureCdnSettingsForm) will have a new textarea field where users can enter multiple CDN endpoints as a comma-separated list. This change will allow administrators to configure multiple endpoints from the module's configuration page without needing to alter code or settings files.

API changes

No direct API changes are anticipated as a result of this update. However, the internal handling of CDN endpoints within the module will change to accommodate multiple endpoints. The purging methods will need to iterate over the list of configured endpoints and apply the purge requests to each one.

Data model changes

The module's configuration data structure will change to store multiple CDN endpoints. Instead of a single endpoint string, the module will now store an array of endpoint strings. This change will require updates to the code that reads and writes these configuration values.