Need to run pattern updater without Drush

Problem/Motivation

The Drush command patternkit:libUpdate updates existing patterns when their schema and/or template changes. We need to be able to run this updater outside of Drush (e.g., in hook_update_N()).

Proposed resolution

Split the main logic of Patternkit's patternkit:libUpdate Drush command into a Drupal service, so that other systems can call them.

Release notes snippet

patternkit:devUpdate Drush Command Removed

The existing drush patternkit:devUpdate command has been removed since it is no longer relevant to active updates of the module and should no longer be in use.

patternkit:libUpdate Drush Command Filtering Now Available

The functionality of the existing drush patternkit:libUpdate command has been split into a pair of new services for improved accessibility to other use within a Drupal site. The commands options have also been revised to offer improved filtering options. Previously, the command excepted a library name intended to filter what patterns might be updated, but unfortunately this value was ignored. Now the command optionally accepts and uses a library name for filtering which patterns should be updated, but it also accepts a new --filter option allowing for limitation of what entity types, bundles, and display modes should be iterated through and updated.

❯ drush help patternkit:libUpdate
Update all patterns in a library.

Examples:
 drush pklu @patternkit           Update all @patternkit library patterns in all blocks and layouts.  
 drush pklu --filter=node.article Update all patterns on the Node Article content type and overrides. 

Arguments:
 [library_name] (optional) The name of a library to limit updates to. 

Options:
 --filter=FILTER A string concatenation of entity type, bundle, and display mode for updates to be limited to.     
                 Example: 'node.article.default'. Fewer items may also be provided to filter. For example, only an 
                 entity and a bundle may be provided ('node.article') or just an entity type ('node').             

Aliases: pklu, patternkit-lib-update

New Service: patternkit.helper.update

A new UpdateHelper service has been added encapsulating much of the functionality that was baked into the previous iteration of the patternkit:libUpdate command. The functionality of the previous iteration of the command has been broken down and implemented on this service as a handful of public methods intended to be versatile and helpful for working with and updating Patternkit components. This service also serves as the entryway to automating the update process for pattern components throughout a site from an update hook, for example.

/**
 * Update all the patterns.
 */
function mymodule_update_9001(&$sandbox) {
  /** @var \Drupal\patternkit\UpdateHelper $update_helper */
  $update_helper = \Drupal::service('patternkit.helper.update');

  [$blocks, $layouts] = $update_helper->updateAllPatternComponents();

  return t('Updated @blocks blocks and @layouts layouts', ['@blocks' => $blocks, '@layouts' => $layouts]);
}

It's also worth noting, the updateAllPatternComponents() method accepts a $filter argument allowing programmatic usage of all the same filter options exposed by the Drush command. An example update hook to only update patternkit patterns on the Article content type might look like this:

/**
 * Update @patternkit patterns on Article Nodes.
 */
function mymodule_update_9001(&$sandbox) {
  /** @var \Drupal\patternkit\UpdateHelper $update_helper */
  $update_helper = \Drupal::service('patternkit.helper.update');

  $filter = [
    'library' => 'patternkit',
    'entity_type' => 'node',
    'bundle' => 'article',
  ];
  [$blocks, $layouts] = $update_helper->updateAllPatternComponents($filter);

  return t('Updated @blocks blocks and @layouts layouts', ['@blocks' => $blocks, '@layouts' => $layouts]);
}

New Service: patternkit.helper.layout

A new LayoutHelper service has also been added to assist with management of Patternkit components placed within layout configurations. Much like the methods on the UpdateHelper service, the methods on the LayoutHelper service are intended to be flexible for usage by other code.

By default, the updateAllPatternComponents() method on the UpdateHelper service will automatically use the LayoutHelper service to also update Layout Builder components if Layout Builder is enabled, so no additional usage of the service is required for that scenario. If, however, one needs to retrieve all of the Patternkit components within a layout or apply a callback function to all the components within a layout, there are helpful methods available on the service to do those tasks.