[Locker] Properties created lazily on LightningElement are not skipped by Locker

[ravijayaramappa]

Description

globalInitialization() is lazily defining aria properties and some standard HTML properties on LightningElement's prototype. This routine is invoked the first time a component has been initialized.

Locker wrapping of LightningElement happens before this. And the wrapping process assumes that all required properties of LightningElement's prototype are defined before the wrapping happens.

Because of the chronology of these two events, all of the lazily defined properties on LightningElement's prototype are not captured in the SecureLightningElement.

Steps to Reproduce

Create a lockerzied module with this structure. Notice the dom tree created, c-child will be created without the id attribute. (note: locker might add some workaround this issue, so talk to the locker team about this issue)

<c-foo>
   <c-child id="child"> </c-child>
</c-foo>

Possible Solution
globalInitialization() should not happen lazily, it should be invoked eagerly. or define all properties of LightningElement's protoype at declaration time.
Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

[ravijayaramappa]

Thanks!