findRelevantNodeReferencesAsNodes should recurse through export assignments

### 🐛 Bug Report

- TypeStat version: 0.6.0
- TypeScript version: n/a
- Node version: n/a

#### Actual Behavior

Right now, `findRelevantNodeReferencesAsNodes` directly calls to the TS language service's `findReferences` API. That only finds _direct_ references to a node. If the node is re-exported with an export assignment (`export { MyNode }`), then only the reference in the export assignment will be looked at.

#### Expected Behavior

Fixers that try to collect all types used for some node are hamstrung by this. You'd expect them to also see uses of the exported node.

#### Reproduction

The `fixReactPropsMissing` fixer added in #1037 doesn't find the `` in this pair of files:

```ts
// MyComponent.ts
const MyComponent = ({ prop }) =>

;
export { MyComponent };
```

```ts
// index.tsx
import { MyComponent } from "./MyComponent";

export const render = () => ;
```