move from IPC to HTTP

[naps62]

Problem

We currently rely on #[tauri::command] to define endpoints to communicate between the UI and the desktop app.
This heavily couples all of our components to tauri, and makes it difficult to work with other layers. e.g.: the app doesn't work on a browser (even though it is running on localhost:1420), largely because of this. It's also impossible to communicate with this endpoints from outside the JS in the webview.

Solution

Create a new iron_http, to live side by side with iron_ws. the root endpoint should behave as an ethereum RPC, and an additional /iron/ namespace should include endpoints for dealing with all the things that are currently tauri commands

the app should now launch both a WS and an HTTP server on boot. Both can be used as an Ethereum provider

Checklist

• Create iron-http crate Add iron-http crate with initial Axum setup #372
• Have root endpoint behave as an Ethereum RPC Correctly respond to JSON-RPC requests on iron-http #377
• Add /iron/ namespace endpoints for responding to tauri commands
  • forge_get_abi Implementing /iron/foundry/abi endpoint #391
  • forge_get_name Implement the /iron/forge/name endpoint #427
  • ws Implement http endpoints for ws commands #421
  • connections Implement the iron/connections endpoints #429
  • networks Implement /iron/networks/ endpoints #430
  • settings Implement /iron/settings/ endpoints #431
  • wallets Implement /iron/wallets/ endpoints #432
  • simulator Implement /iron/simulator/ endpoints #433
  • db Implement /iron/db/ endpoints #439