Harper should correct "seek for" to "seek", "look for", and maybe "seek out"

Just heard a nonnative English speaker on YouTube say "seek for" and realized I've read or seen it a lot and thought we might even have a linter or issue for it already. But I can't find either.

Here are examples:
- I only **seek for** Korean food and my mom had to take me to Korean restaurants
- **Seeking for** a possible work around of a removed feature related to tables
- some errors in requirement.txt, **seeking for** help
- Not a real bug report, but **seeking for** advice.
- **Seeking for** relay that support "On With Timed Off" command.
- **Seeking for** SQL completion proposals
- Correct GetDuration/**Seeking for** VBR Mp3 files without seek headers (XING/VBRI).
- I'll **seek for** help if I have problems in the future :D

But there are potential false positives to avoid flagging:
- SEEK for Android has 18 repositories available.
- Lack of ability to choose slow but exact seek for mp3 on Android.
- See renovate-config-seek for a baseline preset that only maintains SEEK npm packages.
- This is currently done to perform relative seeks for various kinds of seeks
- if I seek for 2s and then instantly after for 2.1s, we should not look for new keyframe
- Benchmarking Agentic Information Seeking for Retrieval-Augmented Generation
- For your use case, it's okay to simply use accurate seek for e.g., vr[100:500]
- Exact seek for mp3 on Android
- Review playback freezes on seek for Hikvision camera

Search Harper's existing linter rules and any prior issue for this phrase, then compare how the listed valid and false-positive examples are handled. Done means correcting the intended uses of “seek for” without flagging product names, technical terminology, or grammatical uses of “seek” followed by “for”.

Written by the indexing model from the issue text.