Run `engine-server` fixture tests with `NODE_ENV=production`

[nolanlawson]

I'm noticing that if I run the fixture tests in prod mode, I get different results than dev mode. This seems partially due to some dev-only accessors defined here:

https://github.com/salesforce/lwc/blob/2b678bbe9c62f6c583745897edc4b46e90908449/packages/%40lwc/engine-core/src/framework/base-bridge-element.ts#L111

This is causing issues with global HTML properties/attributes in particular, but there seem to be some problems with outerHTML as well.

PoC: b89016590

[git2gus[bot]]

This issue has been linked to a new work item: W-17592100

[wjhsf]

It's probably more performant to not define things unnecessarily, but adding empty property descriptors would help avoid subtle foot-guns.

In any case, running engine-server fixture tests with NODE_ENV=production currently has 16 failures. Almost all of them seem to be due to wired data not being provided, a few are around our patches for innerHTML/outerHTML.

If we run NODE_ENV=production yarn test, there are 5 additional failures.