If we find a type that
- we think we can reason about statically
- does not have an __iter__ but can be iterated via __getitem__

we previously just bailed saying that we know it doesn't have an __iter__ method
(instead of calling getiterHelper like we should).  This bug exists on master as well,
but we just don't run into it that often (especially since it's llvm-tier-only).