Add the ability to deactivate the module + handle deletion of a node

@aron this is a great improvement, thanks for MR! Are you able to add a hook_update() to set the new config to TRUE? This way existing sites upgrading the module will not unknowingly disable the purger.

Something like this (untested):

/**
 * Set status to TRUE for Azure CDN Purge settings.
 */
function azure_cdn_purge_update_9104() {
  // Set the default value of the 'status' setting to true.
  \Drupal::configFactory()->getEditable('azure_cdn_purge.settings')
    ->set('status', TRUE)
    ->save();

  // Log the update.
  \Drupal::logger('azure_cdn_purge')->info('Set default status to enabled for azure_cdn_purge.settings.');
}