JS: Improvements from manual data flow investigations

[asgerf]

Adds some missing features I noticed while investigating data flows through some projects:

• Add lodash-es to the lodash model
• Step through babel.transform
• Propagate React components through redux-form
• Add more RouteMatch objects to the react-router model
• Add react-native-base64 to the base64 library
• Model o[o.length] = y as a taint step as it does the same as o.push(y)

Evaluations: (internal links)

• Default slugs shows ok performance.
• The changes were included in an old Redux evaluation and were responsible for the new code injection and request forgery results.

[esbena]

LGTM, with one concern about an async api. (I think it is fine to bundle these unrelated changes into a single PR)

[esbena]

is .transform async? Won't that make the succ turn up as a parameter to a callback?

[asgerf]

Ah you're right. I thought transform would return a promise but after a closer look it just becomes synchronous if you don't give it a callback. There's also transformAsync which does return a promise.

Since neither transformSync nor transformAsync accept a third parameter I just added an extra case for the callback parameter.