Improve combined example baseline alignment

[jmuzina]

Done

Wraps the links/names for examples embedded in combined examples in a p rather than a div. This improves the baseline alignment of combined examples, as the links themselves should not throw the combined example off of the baseline.

Note that individual examples may still throw the combined example off of the baseline, if the component itself has margin/padding issues.

Fixes #5324, WD-14463

QA

• Open any combined example. For example, typography combined.
• Verify that the embedded example links are wrapped in a <p> and have correct paragraph padding & margin.

Check if PR is ready for release

If this PR contains Vanilla SCSS 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 CSS class names are not changed it can be bugfix release (x.x.X)
  • if CSS class names are changed/added/removed it should be minor version (x.X.0)
  • see the wiki for more details
• Any changes to component class names (new patterns, variants, removed or added features) should be listed on the what's new page.

Screenshots

[webteam-app]

Demo

Jenkins

demos.haus

[bartaz]

I don't think it's a huge issue (especially that the main purpose of those is Percy regression testing), but it's a simple improvement.