Optimize performance of maps (with ES3 support)

[rbuckton]

This PR implements the same optimizations as #10270 when in an ES5 or better host environment, while still maintaining support for ES3. This is a port of my changes for the transforms branch that lead to #10270 and can be considered an alternate approach.

The key differences between this and #10270 are:

• hasProperty/getProperty replaced with Map.has/Map.get and MapLike.has/MapLike.get
• Introduced a Map.guard function for use with for..in enumeration which guards on hasOwnProperty in ES3
• Consolidates common Map related functionality in helper functions on the Map and MapLike interfaces.
• Map.create creates an object with a null prototype in ES5+, and a regular object literal in ES3.

Even with the for..in guard, I'm seeing the same performance numbers as in #10270:

• Monaco compile time is approximately 15% faster.
• Angular compile time is approximately 14% faster.
• TFS compile time is approximately 18-20% faster.

[rbuckton]

Closing in favor of #10270.