Fixes #2378 Academicpuma/locales abandoned

[tadean]

Builds are currently failing because academicpuma/locales has reverted to only having a master branch, whereas we require 1.0.0 in our composer.json. This is likely related to the fact that academicpuma/locales was originally a clone of citation-style-language/locales (which was not available on packagist until recently). It appears the maintainer of academicpuma/locales may be intending to abandon the package now that citation-style-language/locales is available on packagist.

This PR does not contain the API-related change of referenced styles discussed in #2313

Related issues

#2378

How to test

• Perform a build
• enable az_publication
• create a publication
• Verify that publication citations still are displayed

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.

[bberndt-uaz]

In Probo I was able to enable the publications module, create a publication, and change the default citation style to display the publication with different styles.