Analyze devirtualized code to determine correct types to resolve

[puff]

The new resolver improvements (#22) are not perfect.

For example, requiring dependencies to resolve generics is not 100% necessary.
Instead, we could analyze the devirtualized code and stack to get the correct type positions. This would likely be easiest by having a new stage to verify and fix types in the devirtualized code. Instead of attempting to guess generic type positions if we can't resolve them, we could mark it and resolve them using analysis to determine the correct positions. Echo would be a great candidate for this.

Same with field types, if we can't resolve the field, we could analyze the code and determine the field type to create a member reference to.

We could also use it for stind/stobj: #7