common: Fix linting

[backspace]

Typechecking wasn’t happening for packages/runtime-common. The commits fix sets of type errors. skipLibCheck is frowned upon by some but used in other packages so ¯_(ツ)_/¯

[github-actions]

Test Results

601 tests  ±0   597 ✔️ ±0   11m 33s ⏱️ -2s
    1 suites ±0       4 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit ba25889. ± Comparison against base commit 9b5eb56.

[github-actions]

Host Tests (In-Memory Index) Test Results

607 tests  ±0   602 ✔️ ±0   10m 20s ⏱️ -57s
    1 suites ±0       5 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 28442dc. ± Comparison against base commit 7a4b13e.

This pull request removes 1 and adds 1 tests. Note that renamed tests count towards both.

Chrome 124.0 ‑ Acceptance | interact submode tests > 1 stack > when permission is updated after user has obtained the token: retrieve a new JWT if recevive 401 error

Chrome 124.0 ‑ Acceptance | interact submode tests > 1 stack > when permission is updated after user has obtained the token: retrieve a new JWT on  401 error

♻️ This comment has been updated with latest results.

[github-actions]

Host Tests (DB Index) Test Results

607 tests  ±0   604 ✔️ ±0   11m 41s ⏱️ +23s
    1 suites ±0       3 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 28442dc. ± Comparison against base commit 7a4b13e.

This pull request removes 1 and adds 1 tests. Note that renamed tests count towards both.

Chrome 124.0 ‑ Acceptance | interact submode tests > 1 stack > when permission is updated after user has obtained the token: retrieve a new JWT if recevive 401 error

Chrome 124.0 ‑ Acceptance | interact submode tests > 1 stack > when permission is updated after user has obtained the token: retrieve a new JWT on  401 error

♻️ This comment has been updated with latest results.

[habdelra]

I’m fine with this (I’m probably the one that started using skipLibCheck in the first place). There is a trade off. Type issues in any external imports (which include imports from other workspaces in our repo), will be ignored. So long as we are comfortable with this I think it’s fine. Since we are running type checks in all the TS workspaces in our repo I think we have our bases covered.