Correct confusing "over time" and "overtime"

**The Error**

Very often I see people using the noun "overtime" (work beyond your normal hours paid at a higher rate) when they mean the adverb "over time" (gradually).

The reverse probably happens but I haven't noticed it.

**Examples:**
1. **Overtime**, I raised the price and built up to 4 licensing levels.
2. Initially the focus will be on simple implementations but **overtime** we can hopefully add more complex context and controls as well.
3. they don't need a whole schema to be defined and the schema's are changing **overtime**
4. Starting is simply that, but **overtime** I would like to make it more simple to do that
5. **overtime**, I guess we will see sha256 and some other hash function to have open source implementation in cairo-lang
6. Does it slowly happen **overtime** and keeps getting worse?

While looking for examples I found different kinds of wrong uses:
- When a long-time task was **overtime**, seems the memory was chaotic that some invalid input and output was generated. (meaning the task ran longer than expected or missed some cutoff time?)

No files or tests are named. Start by locating the existing handling and tests for “overtime” and “over time”; use the listed examples to determine the intended distinction, then add coverage showing gradual-change uses are corrected or flagged while noun uses remain valid.

Written by the indexing model from the issue text.