resolvedProperties in schemas are barely populated & consuming memory because of the default HashMap constructor #879
Description
DataSchema._resolvedProperties & RecordDataSchema$Field._resolvedProperties have been reported in our use cases within LinkedIn as consuming too much memory due to the unnecessarily-large HashMaps. If most use cases also don't use resolvedProperties that much, we should be able to initialize them to 0 to start with, and let them resize based on usage