fix: Refactor ctx

[SgtPooki]

ctx probably still needs some additional optimizations, but this is a significant improvement

May help with #2113

fixes #1177

[SgtPooki]

The failing workflow (ci / test (macos-latest)) runs correctly locally, so I am restarting that job

npm run test:e2e

> ipfs-desktop@0.20.5 test:e2e
> xvfb-maybe cross-env NODE_ENV=test playwright test test/e2e/launch.e2e.test.js


Running 10 tests using 1 worker

  ✓  test/e2e/launch.e2e.test.js:66:3 › Application launch › creates a repository on startup (5s)
  ✓  test/e2e/launch.e2e.test.js:80:3 › Application launch › starts fine when node is already running (4s)
  ✓  test/e2e/launch.e2e.test.js:88:3 › Application launch › applies config migration (MDNS.enabled) (4s)
  ✓  test/e2e/launch.e2e.test.js:109:3 › Application launch › applies config migration (Web UI CORS 1) (4s)
  ✓  test/e2e/launch.e2e.test.js:131:3 › Application launch › applies config migration (Web UI CORS 2) (4s)
  ✓  test/e2e/launch.e2e.test.js:152:3 › Application launch › applies config migration (Web UI CORS 3) (4s)
  ✓  test/e2e/launch.e2e.test.js:173:3 › Application launch › applies config migration (ConnMgr) (4s)
  ✓  test/e2e/launch.e2e.test.js:194:3 › Application launch › starts with repository with "IPFS_PATH/api" file and no daemon running (6s)
  ✓  test/e2e/launch.e2e.test.js:210:3 › Application launch › starts with multiple api addresses (4s)
  ✓  test/e2e/launch.e2e.test.js:222:3 › Application launch › starts with multiple gateway addresses (4s)

  Slow test file: test/e2e/launch.e2e.test.js (42s)
  Consider splitting slow test files to speed up parallel execution

  10 passed (42s)

[SgtPooki]

I was able to install and run the dmg from the action artifact files at the bottom of https://github.com/ipfs/ipfs-desktop/actions/runs/2240299896.

There are a few issues I'm seeing with the application, below is the content from the logs:

2022-04-29T10:07:24.871Z info: [meta] logs can be found on /Users/sgtpooki/Library/Application Support/IPFS Desktop
2022-04-29T10:07:29.330Z error: The 'screen' module can't be used before the app 'ready' event
2022-04-29T10:07:29.339Z error: dialog module can only be used after app is ready
2022-04-29T10:07:29.339Z error: dialog module can only be used after app is ready
2022-04-29T10:07:29.339Z error: dialog module can only be used after app is ready

Which wasn't occurring with npm start. I will work around these errors using the approach mentioned at electron/electron#5897 (comment)

[hacdias]

@SgtPooki what's the status on this?

[SgtPooki]

@SgtPooki what's the status on this?

I've had to de-prioritize this due to other work, but I plan on picking this back up as time becomes available outside of the kubo-rpc-client work.

[SgtPooki]

superseded by #2378