Catch "into" used when it should be "in"

**The Error**
This seems fairly new to me in recent years, mostly non-native speakers, but also some younger native speakers.

**Examples:**
1. Can not open .txt files **into** retropad from file explorer → Can not open .txt files **in** retropad from file explorer
2. That code doesn't **belong into** any trait. → That code doesn't **belong into** any trait.
3. The absence of abstractions **results** by definition **into** bigger code constructs than in other languages → The absence of abstractions **results** by definition **in** bigger code constructs than in other languages
4. ... because at first it was too low, which resulted into some issues for me I didn't really foresee.

**Apparently the opposite also happens:**
1. 11 years after they have been introduced **into** the language → 11 years after they have been introduced **to** the language

**Potential Edge Cases**

There are probably many false positives that would need to be sifted out.

Review the reported “into”/“in” and “into”/“to” examples, then inspect Harper’s existing grammar rules and false-positive handling. Define the accepted corrections and add coverage for the examples and relevant edge cases; done means the intended misuse is caught without changing valid uses.

Written by the indexing model from the issue text.