Review/enforce possible values / types of tracked object properties

In ObjectValue.js, there's a list of trackedPropertyNames.

Tracked objects must be void or a (subtype of a) Value. After state joins, an AbstractValue may appear (encoding a conditional expression), or possibly other Value kinds due to simplification rules. Maybe there's some special logic in place for arrays (otherwise, how does $MapData and $SetData and $WeakMapData and $WeakSetData work as tracked objects?)

We should...

• Document the actual requirements where trackedPropertyNames is defined
• Consider including type information in trackedPropertyNames and issuing type invariant checks as part of the property injection in setupTrackedPropertyAccessors.
• Manually review all static Flow types of tracked properties to check if they conform