Hi there, after upgrading to the latest version the autofix does not automatically includes the missing deps, is this the expected behavior? I didn't find any release notes of the lib so I couldn't check if that was expected, also, I'd say, if done on purpose, this change should be on a major version, shouldn't it?

## The current behavior 2.4.0 or above
Some deps are missing.
![image](https://user-images.githubusercontent.com/4994258/76088672-2ee9dc00-5f97-11ea-988a-8b6bb36c74d0.png)

Quick fix shows:
![image](https://user-images.githubusercontent.com/4994258/76088711-42954280-5f97-11ea-990c-5a113b27013b.png)
`eslint --fix` shows:
![image](https://user-images.githubusercontent.com/4994258/76088908-99028100-5f97-11ea-81e7-1a9fe4175881.png)

But code is not being updated, although if I manually click it add the missing deps.

## Expected behavior, 2.3.0

Noticed it shows another context menu:
![image](https://user-images.githubusercontent.com/4994258/76089526-918fa780-5f98-11ea-9b88-6d88a0550c8c.png)

Also it does add the missing deps using the same `eslint --fix` command.
if (node === calleeNode && options && options.additionalHooks) {
        
        
        let name;
        try {
          name = toPropertyAccessString(node);
        } catch (error) {
          if (/Unsupported node type/.test(error.message)) {
            return 0;
          } else {
            throw error;
          }
        }
        return options.additionalHooks.test(name) ? 0 : -1;
      } else {
        return -1;
      }
  }
}
/**
 * ESLint won't assign node.parent to references from context.getScope()
 *
 * So instead we search for the node from an ancestor assigning node.parent
 * as we go. This mutates the AST.
 *
 * This traversal is:
 * - optimized by only searching nodes with a range surrounding our target node
 * - agnostic to AST node types, it looks for `{ type: string, ... }`
 */
function fastFindReferenceWithParent(start, target) {