:eyes: status for hard to analyze instances

For some codebases, some of the goroutine searches seem to be really hairy (they're actually just a BFS tree being printed in an exceptionally lazy manner).

If we *really* want to see them analyzed, we're going to need to visualize them like trees. This means laying them out as trees either in a textual format (which VetBot could do) or using some other tool.

One strategy even if the output becomes easier to parse could be to add a new label for issues whose callgraphs may be much too complicated and need further analysis. We can sequester them and learn how to deal with them later.

With that in mind, I think adding a new :eyes: status will allow us to set aside issues that are going to need additional data crunching in order to classify. The point here isn't to kick the can down the road, we might learn that there aren't enough issues that fall into this category to justify a significant development effort.

This is open for discussion.