fix(css): add nolint and increase output heights

[OnkarRuikar]

• addresses correct html closing tag (typo) #37217 (comment)

Increase live sample output heights to avoid scrolling. Also, add nolint to the code block to prevent weird formatting.

/cc @chrisdavidmills

[github-actions]

Preview URLs

• /en-US/docs/Web/HTML/Element/summary

[Josh-Cena]

I'm a personal -1 on disabling the formatter here. -nolint is meant for cases where the code must not be formatted, such as syntax blocks or purposefully demonstrating whitespace differences. If we just subjectively decide that "because the formatting is not good enough here, let's not format it", then we are in a worse state than not having a formatter at all, because now we have even more bikeshedding than before: do we nolint or not? If we do, then how do we format it? The goal of a formatter is not to make something everyone finds beautiful, but something that's both predictable and doesn't change program semantics. I don't feel strongly enough to block this PR, but it opens a path I'm not happy for us to go down.

[OnkarRuikar]

This is not the first case. Many CSS and HTML code blocks have been marked -nolint (from the start) because manual formatting looks way better.

• content/files/en-us/learn/css/building_blocks/advanced_styling_effects/index.md

  Lines 99 to 123 in 5c5b3ab

  	```css-nolint
  	p {
  	margin: 0;
  	}
  	article {
  	max-width: 500px;
  	padding: 10px;
  	background-color: red;
  	background-image: linear-gradient(
  	to bottom,
  	rgb(0 0 0 / 0%),
  	rgb(0 0 0 / 25%)
  	);
  	}
  	.multiple {
  	box-shadow: 1px 1px 1px black,
  	2px 2px 1px black,
  	3px 3px 1px red,
  	4px 4px 1px red,
  	5px 5px 1px black,
  	6px 6px 1px black;
  	}
  	```

• content/files/en-us/learn/html/introduction_to_html/advanced_text_formatting/index.md

  Lines 300 to 307 in e2a558f

  	```html-nolint
  	<p>
  	According to the
  	<a href="/en-US/docs/Web/HTML/Element/blockquote">
  	<cite>MDN blockquote page</cite></a>:
  	</p>
  	<blockquote

nolint is meant for cases where the code must not be formatted, such as syntax blocks or purposefully demonstrating whitespace differences.

Out of 4k+ -nolints in the repo, you'll find very few fit this criteria.

[Josh-Cena]

This is not to say these cases are fair either, but their existence is why my opinion is not strong enough to fully block this PR. If you search by (?<!## Syntax\n\n)```\w+-nolint(?! example-bad), you'll find significantly fewer cases, many of which are still either actually unformattable JS snippets or SVG disguised as HTML so they get rendered by live examples.

[OnkarRuikar]

This is not to say these cases are fair either,

For a better reader experience, we need to make some exceptions.

[chrisdavidmills]

Thanks, @OnkarRuikar, that's much better!