[WIP] Bump typescript from 6.0.3 to 7.0.2

[Copilot]

Thanks for the feedback on #69. I've created this new PR, which merges into #69, to address your comment. I will work on the changes and keep this PR's description up to date as I make progress.

Original PR: #69
Triggering comment (#69 (comment)):

@copilot please look into all the failing checks and see if we can fix. feel free to open a PR. these failures are likely because of typescript 7 updates - let's try to figure out how much effort it'll take to keep typescript 7 and fix these failures.

[abdulahmad307]

@copilot so what changed here? theres still a failing workflow and the PR says 0 files changed

[Copilot]

@copilot so what changed here? theres still a failing workflow and the PR says 0 files changed

Confirmed: my previous commit ("Initial plan") only contained the plan checklist and no actual code changes, which is why the diff showed 0 files changed and the workflow is still failing.

I investigated the failure: typescript-eslint@8.65.0 (the latest release) declares a peer dependency of typescript@">=4.8.4 <6.1.0", so it's incompatible with TypeScript 7.0.2 and npm install/npm ci fails outright with an ERESOLVE conflict. There's no newer typescript-eslint release that supports TS7 yet — the maintainers have said support is blocked on TypeScript 7.1 stabilizing its new programmatic (Corsa) API (see typescript-eslint/typescript-eslint#12518). ts-jest and other tools that use TS internals are in the same boat.

Given that, keeping typescript-eslint working with TS 7.0.2 isn't feasible right now without pinning to a pre-release/patched fork or disabling the lint workflow's peer-dep enforcement. I'll hold off on further changes to this PR until we decide direction — happy to either (a) close this out and keep TypeScript at 6.0.3 until typescript-eslint adds support, or (b) upgrade with --legacy-peer-deps as a stopgap if that's acceptable. Let me know which you'd like.

[abdulahmad307]

i dont think this is doable right now