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?

There is nothing wrong with the concise style for `case` clauses used consistently throughout Ramda. This is an issue with the style checker, not with the code and I think we should not change valid and readable code because of a limitation in a style checker.

The proposed change also makes the code much less readable, IMHO.