Use html-element-attributes and svg-element-attributes

[nolanlawson]

This affects attribute validation in @lwc/template-compiler, which currently surfaces as warnings.

The libraries html-element-attributes and svg-element-attributes contain mappings of valid HTML tag/attribute pairs. They each have ~70-80k weekly npm downloads and seem fairly up-to-date.

Currently we are using a vendor'ed copy of the first:

lwc/packages/@lwc/template-compiler/src/parser/utils/html-element-attributes.ts

Lines 34 to 43 in 2ddff92

	const HTML_ELEMENT_ATTRIBUTE_MAP = {
	'*': [
	'accesskey',
	'autocapitalize',
	'class',
	'contenteditable',
	'dir',
	'draggable',
	'enterkeyhint',
	'hidden',

... and for the second, we are just assuming that all known SVG elements are good, regardless of what attributes they have:

lwc/packages/@lwc/template-compiler/src/parser/attribute.ts

Line 222 in dba53e7

SUPPORTED_SVG_TAGS.has(tagName) ||

lwc/packages/@lwc/template-compiler/src/parser/constants.ts

Lines 58 to 61 in 9246638

	export const SUPPORTED_SVG_TAGS = new Set([
	'svg',
	'a',
	'altGlyph',

Rather than maintaining our own list of valid html tag/attribute mappings (which can get out-of-date or be inaccurate), we should pool efforts with a reliable third-party package like these ones.

Unfortunately these two packages both switched to ESM recently, so we would need to solve #3017 first.

[nolanlawson]

We have a solution for ESM now; we can inline things. However, this might be an observable change, so worth validating that.