Fix Map/Set creation via the API with nosnap build

Fix Map/Set creation via the API with nosnap build

The Map and Set maps get overwritten when collection.js executes, so in
a nosnap build we have to wait until it runs before we grab the maps.
To facilitate that, store the functions in the native context as well.

Committed: https://crrev.com/dd4cd1fe90c7d6a445706950663cf38d79af9403
Cr-Commit-Position: refs/heads/master@{#28743}

[adamk, 2015-06-01 21:27:07]

adamk@chromium.org changed reviewers:
+ jochen@chromium.org

[adamk, 2015-06-01 21:29:17]

The CQ bit was checked by adamk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-06-01 21:29:47]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1161363002/1

[jochen (gone - plz use gerrit), 2015-06-01 21:30:09]

lgtm

[commit-bot: I haz the power, 2015-06-01 23:04:41]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-06-01 23:04:42]

Dry run: This issue passed the CQ dry run.

[adamk, 2015-06-01 23:12:52]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2015-06-01 23:13:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1161363002/1

[commit-bot: I haz the power, 2015-06-01 23:16:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-01 23:16:49]

Patchset 1 (id:??) landed as
https://crrev.com/dd4cd1fe90c7d6a445706950663cf38d79af9403
Cr-Commit-Position: refs/heads/master@{#28743}