wrong `composes` for propType objects that are wrapped

Hello!

when defining prop types people do all sorts of things, for example:

import omit from 'lodash/omit';
import OtherComponent from 'important/path';

export default class Component extends React.PureComponent {
  propTypes = {
    ...omit(OtherComponent.propTypes, ['exclude', 'us']),
    something: bool
  };

  // ...
}

Expected

composes array is ['important/path']

Actual

composes array is ['lodash/omit']

i'm not even sure how this should be handled.
In example above it seems that extracting first argument from function
should be enough. But what if the composed prop types are not first
argument?

Should react-docgen support such cases at all? It seems valid to do so
from JS perspective but generated documentation is incomplete.

Recently https://github.com/reactjs/react-docgen/issues/248 was closed, so perhaps this issue should be considered too.

Thanks for the library!

Start by tracing how react-docgen derives the composes array from wrapped prop-type expressions, using the omit(OtherComponent.propTypes, ...) example as the reproduction. Compare the expected important/path result with the actual lodash/omit result and determine how non-first composed arguments should be handled. Done means the behavior is defined and covered for the supported wrapped-expression cases.