Library makes no distinction between utilities and traversal methods with the same name

[edg2s]

(moved from dgraham/eslint-plugin-jquery#29, project assumed inactive)
There are two separate methods called 'each' with different documentation pages:

• https://api.jquery.com/jquery.each/
• https://api.jquery.com/each/

The same is true of 'map':

• https://api.jquery.com/jQuery.map/
• http://api.jquery.com/map/

Update: This task applies to every rule that uses createCollectionOrUtilMethodRule. Although often the utils are not officially documented, some will be getting deprecated in the future (e.g. $.find):

• no-attr
• no-clone
• no-css
• no-data
• no-each
• no-filter
• no-find
• no-map
• no-prop
• no-text

[edg2s]

cc @Krinkle @jdforrester @jdlrobson

We need to come up with a new naming scheme to resolve these conflicts, currently the only rule is:
no-[method-name]

A couple of options:

1. no-each-method & no-each-util
2. no-collection-each & no-util-each
3. stick with no-each for both and use config options
4. no-each & no-jquery-each

4 would necessarily be a breaking change, but I'm not that concerned about that. In 1/2 we could leave no-each as is, or deprecated/remove it.

Thoughts?

[jdforrester]

My preference order is 2 > 1 > 3 > 4.

[edg2s]

I'd probably go with no-each-[modifier] so they appear next to each other when listed.