docs(patterns): Pattern elements docs describe content, not API

[jmuzina]

Done

Updates the "elements" documentation of some patterns that were previously describing their APIs instead of their elements. The idea is that pattern elements docs should focus on the elements that compose the patterns, not their APIs. A separate API section describes the parameters at a more engineering level.

Fixes WD-31507
Fixes #5698

QA

• Review documentation of updated patterns and ensure the "elements" section is clear and only describes high-level lists of content that is passed to the pattern. Also ensure that the Jinja API section fully describes the API and no API information that was previously in the elements section has been lost.
  • Equal heights
  • Linked logo section
  • Pricing block

Check if PR is ready for release

If this PR contains Vanilla SCSS or macro code changes, it should contain the following changes to make sure it's ready for the release:

• PR should have one of the following labels to automatically categorise it in release notes:
  • Feature 🎁, Breaking Change 💣, Bug 🐛, Documentation 📝, Maintenance 🔨.
• Vanilla version in package.json should be updated relative to the most recent release, following semver convention
  • if existing APIs (CSS classes & macro APIs) are not changed it can be a bugfix release (x.x.X)
  • if existing APIs (CSS classes & macro APIs) are changed/added/removed it should be a minor version (x.X.0)
  • see the wiki for more details
• Any changes to component class names (new patterns, variants, removed or added features) or macros should be listed on the what's new page.

[webteam-app]

Demo

Jenkins

demos.haus

[jmuzina]

Content approved via MM message by @Sophie-32 - will still need GitHub approval by another engineer CC @advl