Closes #5275 Adds Mercury Editor 2.2.5

[ewlyman]

Description

Adds the 2.x versions of Layout Paragraphs and Mercury Editor modules to Quickstart

Release notes

Related issues

Closes #5275

How to test

Note: The 2.x version of Mercury Editor and Layout Paragraphs experiences issues editing content if your multidev has the Workspaces module enabled.

1. Enable Mercury Editor -- you will be prompted to enable dependencies, it's safe to do so.
2. Under Configuration, go to Mercury Editor settings and select Page and Person under "Content" and save configuration -- these two content types are useful for demonstrating M.E. but you can also try others.
3. Under Structure -> Content types -> Page select Manage form display
4. Set the format for Page Elements to Layout Paragraph and save
5. Under Configuration -> Performance clear all caches
6. Visit any Page or Person content and select "Edit" to test the editor interface
7. Add page content. By selecting the + sign, you should see a list of paragraph types you can add to the page.
8. When editing/adding person content, you can view your changes in the wysiwyg interface by clicking the 'Save' button at top right. 'Done' will return you to your content.

Optional - Test Mercury Editor with Layout Paragraphs front-end editor

1. Under Structure -> Content types -> Page select Manage display
2. Set the format for Page Elements to Layout Paragraphs Builder (experimental) and save.
3. Under Configuration -> Performance clear all caches
4. Visit a page with paragraphs on it.
5. Hover over the paragraphs; you can click the "Edit Page Elements" button to enter the front-end editor.
6. Please note that only paragraphs in Pages can be edited from the front-end.

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.