Replace $.each with Array.prototype.forEach.

[RaymondLim]

This fixes issue #1098

[peterflynn]

Typo: froEach -> forEach

[peterflynn]

We seem inconsistent about iterating jQuery objects, which are array-like but not plain vanilla arrays.

• In CodeHintManager we used to use $.each(), but this patch changes it to .forEach()
• In InlineTextEditor we still use $.each()
• In WorkingSetView & ProjectManager we use .each()
  (note the distinction: $.each() takes the jQ object as an argument, while .each() is a method on the jQ object).

@rwldrn, what's the best convention here in your opinion? My assumption would be: .forEach() for "true" arrays, .each() for jQuery objects, and $.each() only for objects/maps. Does that sound right?

[peterflynn]

One other note: we also have a few places where $.each() is used to iterate objects/maps, but the inner function misleadingly names its first argument "index," which suggests it's iterating an array when it's not. SpecRunnerUtils and BootstrapReporter both have this problem.

[peterflynn]

p.s. if these are too many changes to sneak in on the last day of the sprint, I think it's fine to push this out to sprint 12. Better to wait a couple more days and get everything fully cleaned up IMHO.

[RaymondLim]

@peterflynn, I'll push this out to sprint 12 so that we can wait for @rwldrn opinion and do extra cleanup that you pointed out.

[rwaldron]

I'm flattered 😊 that you thought of me

[pthiess]

:) @rwldrn Rick, don't miss the opportunity to share your opinion.

[peterflynn]

@rwldrn, well you did file the original bug in this case... :-)

[RaymondLim]

Closing this pull request since we need to do other cleaning that Peter mentioned.