Update dependency eslint-plugin-react to version 6.10.3

[renovate-bot]

This Pull Request updates dependency eslint-plugin-react from version 6.10.0 to 6.10.3

Changelog

6.10.3 / 2017-03-20

• Update CHANGELOG and bump version
• Revert "[Fix] jsx-indent with tabs (fixes #1057)"
  This reverts commit 6e5f688065aa218d71742dc4b31929c16ab1078d.
  Conflicts:
  lib/rules/jsx-indent.js
  tests/lib/rules/jsx-indent.js

6.10.2 / 2017-03-19

• Update CHANGELOG and bump version
• Fix jsx-indent indentation calculation with nested JSX (fixes #1117)

6.10.1 / 2017-03-19

• Update CHANGELOG and bump version
• Fix nextProps false positive in no-unused-prop-types
• Merge pull request #1089 from benstepp/bs-multicomp-false-positives
  Bug fix for false positives with no-multi-comp

• Bug fix for false positives with no-multi-comp
  Previously, when createElement was destructured from React, it would
  cause any function defined in the file to be flagged as a React
  Component. This change makes it such that the function must call
  createElement to be considered a component.
  Fixes #1088

  Review: Use object.assign with sourceType: module in the added test over
  babel-eslint.
• [Fix] Update void-dom-elements-no-children createElement checks
  Merge pull request #1080 from jomasti/issue-1073
• Merge pull request #1081 from webOS101/jsx-indent-fix
  Fix jsx-indent single line jsx
• Fix jsx-indent single line jsx
  Also adds test
• Update void-dom-elements-no-children
  This ensures that the rule only checks for a `createElement` call from
  React. It will also prevent the rule from failing when it hits a
  `createElement` that only has an element as an argument.
• Merge pull request #1077 from iancmyers/fix-jsx-indent-template-conditional
  Fix error caused by templates in ConditionalExpressions (jsx-indent)
• Fix error caused by templates in ConditionalExpressions (jsx-indent)
  Template strings are constructed differently from other tokens in
  espree. Other tokens are created by the Token class and are thus
  Token class objects. They look like this:
  ```
  Token {
  type: 'String',
  value: '"bar"',
  start: 44,
  end: 49,
  loc:
  SourceLocation {
  start: Position { line: 4, column: 11 },
  end: Position { line: 4, column: 16 } },
  range: [ 44, 49 ] }
  ```
  Template tokens, however, are constructed differently and end up as
  plain JavaScript objects, which look like this:
  ```
  { type: 'Template',
  value: '`bar`',
  loc:
  { start: Position { line: 4, column: 11 },
  end: Position { line: 4, column: 16 } },
  range: [ 44, 49 ] }
  ```
  See: espree's token-translator.js
  As a result of this different construction, the `start` and `end`
  properties are not present on the template token object. To correct this
  I've changed to using the `range` property, which I infer to be more
  proper given the method it is being passed into is called
  `getNodeByRangeIndex`. I also think we can safely rely on `range` being
  present on all token types.
  Fixes #1061
• Merge pull request #1058 from kentcdodds/pr/jsx-indent-tabs-fix
  [Fix] jsx-indent with tabs