Fixes #5669 AZ SEO metatag defaults drush command

[tadean]

Description

This PR provides a drush convenience command for setting metatag defaults: az-seo:tag

This would be mostly unnecessary (and could be accomplished with config:set) aside for the fact that schema_organization_parent_organization is stored as serialized php. This drush command attempts to provide a config:set-alike interface for the serialized element.

Release notes

Added `az-seo:tag` Drush command for setting metatag defaults.

Related issues

#5669

How to test

• install site
• drush az-seo:tag --help
• drush az-seo:tag schema_organization_name sitename
• drush az-seo:tag schema_organization_parent_organization.@id https://quickstart.arizona.edu
• Verify the above changes are reflected in the global metatag defaults (/admin/config/search/metatag)

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.

[tadean]

• Determine if this command is necessary (see: config:set, serialized PHP in schema_organization_parent_organization)
• Determine interface for portfolio management (single tag at a time, all tags at once, merge behavior, etc)
• Determine release scoping. This is a new feature to a non-experimental module, but is Drush-only