feat: add Optimism as separate N-API package

[Wodann]

This PR restructures the edr_napi_core and edr_napi to be able to share code with the new edr_napi_optimism package.

I ran into one problem that I was able to solve. Namely, when a crate that generates NAPI bindings is added as a dependency to another crate that generates NAPI bindings, the test target of the dependant crate will throw linker errors. This is a known issue. I was only able to work around it by adding the recommended rustflags to both the workspace- and project-level .cargo/config.toml. If I only added it to the project, the cargo test --all-features --all-targets --workspace command would still throw the linker errors.

There is currently still a bug in the edr_napi_optimism JS tests. In the background, the hyper Client is sporadically trying to execute a future using its executor. By default, this executor uses tokio::spawn but since the edr_optimism NPM package doesn't have a tokio runtime, this panics.

thread '' panicked at /home/vscode/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/common/exec.rs:49:21:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

The solution is to specify a custom executor, but reqwest always uses the Tokio executor. An issue exists to add this executor, but a previous PR was rejected because it was deemed unnecessary.

For now, my proposal would be to merge the changes to the project layout and move forward with the release of the GenericChainSpec, as edr_optimism won't be exposed anyway.

A future issue can then:

1. fork reqwest
2. add setting of the executor
3. set the executor with the tokio::Runtime of our edr NPM package's runtime

Could you please pay special attention to these two aspects when reviewing?

[changeset-bot]

⚠️ No Changeset found

Latest commit: a313a49

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Wodann]

cargo was reporting that this setting was ignored. Only the workspace Cargo.toml's profile are respected.

[Wodann]

This is required for edr_napi_optimism to use this crate as a dependency

[Wodann]

File moved from edr_napi, with a modification to the config. This removes the dependency on napi types.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1193 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@05a8cb6). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
crates/edr_napi_core/src/logger.rs	0.00%	879 Missing ⚠️
crates/edr_napi/src/logger.rs	0.00%	61 Missing ⚠️
crates/edr_napi_core/src/provider/config.rs	0.00%	56 Missing ⚠️
crates/edr_napi_core/src/provider.rs	0.00%	43 Missing ⚠️
crates/edr_napi_core/src/spec.rs	0.00%	32 Missing ⚠️
crates/edr_napi_core/src/subscription.rs	0.00%	28 Missing ⚠️
crates/edr_napi/src/provider/response.rs	0.00%	19 Missing and 2 partials ⚠️
crates/edr_napi_optimism/src/factory.rs	0.00%	18 Missing ⚠️
crates/edr_optimism/src/spec.rs	0.00%	11 Missing ⚠️
crates/edr_napi/src/subscription.rs	0.00%	10 Missing ⚠️
... and 8 more

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #659   +/-   ##
=======================================
  Coverage        ?   63.07%           
=======================================
  Files           ?      216           
  Lines           ?    23689           
  Branches        ?    23689           
=======================================
  Hits            ?    14941           
  Misses          ?     7819           
  Partials        ?      929           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Wodann]

This should not have any adverse side-effects, as we also manually pass this argument to cargo clippy which should fail if there are any warnings.

For reference:

cargo clippy --workspace --all-targets --all-features -- -D warnings