style: normalize formatting

__Pro-tip:__ Append `?w=` to the URL when viewing these changes to see a meaningful diff.

---

Overview:

  - normalize function formatting:
      - function statement: `function f() {}`
      - function expression: `function() {}`

  - `disallowQuotedKeysInObjects: true` (e.g. `{foo: 42}` rather than `{'foo': 42}`)

  - `requireSpaceAfterLineComment: true` (e.g. `// comment` rather than `//comment`)

  - `validateIndentation: 4`

I prefer two spaces for indentation, and this style is currently used in some of the project's files, but __ramda.js__ itself uses four spaces so I went with that. If you'd like to switch to two spaces I'll update this pull request. :)

How is __ramda.api.js__ used?

I don't know if the jscs tool has a strong preference for a certain grouping of these nested functions, but here I would much rather keep the logical ordering of:

    associative: function(obj, f, g) {
        return obj.chain(f).chain(g).equals(
            obj.chain(function(x) { return f(x).chain(g); })
        );
    }

Although I'm fine with switching to a universal 4-spaces throughout the codebase.  The question is whether it will scream about this as bad style for some reason.  If so, I'm inclined to turn off whatever rule or rules enforce that.