fix: avoid circular reference when resolving name from within assignment

[motiz88]

When calling resolveToValue, currently it may resolve to an expression containing the very reference we were trying to resolve, even though the correct resolution in terms of program flow is an earlier assignment. In particular, this arises in some handlers when we reassign a variable holding a component, e.g when wrapping it with a HOC:

import React from 'react';
let Component = (props, ref) => {};
//              ^
//              expected resolution
Component = React.forwardRef(     Component     );
//          ^                     ^
//          actual resolution     reference

Here, we minimally tweak resolveToValue to (1) take an Identifier path instead of a name; and (2) not resolve to an assignment expression's RHS if the assignment contains the reference we're trying to resolve. Note that this isn't a complete solution for tracking reassignments (e.g. it doesn't account for ordering or more complex ASTs) but it should be a satisfactory fix for this particular pattern.