chore(schema-engine): get rid of toml -> Rust generation in `json…

…-rpc-api-build`, which is now compatible with `wasm32-unknown-unknown` (#5224)

This PR:
- Closes
[ORM-778](https://linear.app/prisma-company/issue/ORM-778/get-rid-of-toml-rust-generation-in-json-rpc-api-build-enable-wasm)
- Gets rid of `toml` -> `Rust` generation in `json-rpc-api-build`. Toml
definitions are substituted with equivalent Rust struct/enum
declarations, avoiding all the previous build-time shenanigans.
- You can see the previous expanded macro in
b1efb11.
- Renames `json-rpc-api-build` into `json-rpc-api`
- Enables `wasm32-unknown-unknown` usage of `json-rpc-api`

/integration

---------

Co-authored-by: jkomyno <[email protected]>

Cargo.toml

@@ -5,7 +5,7 @@ members = [
     "schema-engine/core",
     "schema-engine/connectors/*",
     "schema-engine/datamodel-renderer",
-    "schema-engine/json-rpc-api-build",
+    "schema-engine/json-rpc-api",
     "schema-engine/mongodb-schema-describer",
     "schema-engine/sql-migration-tests",
     "schema-engine/sql-introspection-tests",

schema-engine/core/Cargo.toml

@@ -16,6 +16,7 @@ user-facing-errors = { workspace = true, features = [
     "quaint",
 ] }
 
+json-rpc = { path = "../json-rpc-api", package = "json-rpc-api" }
 async-trait.workspace = true
 chrono.workspace = true
 enumflags2.workspace = true
@@ -28,8 +29,5 @@ tracing-subscriber.workspace = true
 tracing-futures.workspace = true
 url.workspace = true
 
-[build-dependencies]
-json-rpc-api-build = { path = "../json-rpc-api-build" }
-
 [features]
 vendored-openssl = ["sql-schema-connector/vendored-openssl"]

schema-engine/core/src/api.rs

@@ -1,6 +1,7 @@
 //! The external facing programmatic API to the schema engine.
 
-use crate::{commands, json_rpc::types::*, CoreResult};
+use crate::{commands, CoreResult};
+use json_rpc::types::*;
 
 /// The programmatic, generic, fantastic schema engine API.
 #[async_trait::async_trait]

schema-engine/core/src/lib.rs

@@ -4,7 +4,7 @@
 
 //! The top-level library crate for the schema engine.
 
-include!(concat!(env!("OUT_DIR"), "/methods.rs"));
+pub use json_rpc;
 
 // exposed for tests
 #[doc(hidden)]

schema-engine/core/src/rpc.rs

@@ -1,4 +1,5 @@
-use crate::{json_rpc::method_names::*, CoreError, CoreResult, GenericApi};
+use crate::{CoreError, CoreResult, GenericApi};
+use json_rpc::method_names::*;
 use jsonrpc_core::{types::error::Error as JsonRpcError, IoHandler, Params};
 use psl::SourceFile;
 use std::sync::Arc;

schema-engine/core/src/state.rs

@@ -3,10 +3,9 @@
 //! Why this rather than using connectors directly? We must be able to use the schema engine
 //! without a valid schema or database connection for commands like createDatabase and diff.
 
-use crate::{
-    api::GenericApi, commands, json_rpc::types::*, parse_configuration_multi, CoreError, CoreResult, SchemaContainerExt,
-};
+use crate::{api::GenericApi, commands, parse_configuration_multi, CoreError, CoreResult, SchemaContainerExt};
 use enumflags2::BitFlags;
+use json_rpc::types::*;
 use psl::{parser_database::SourceFile, PreviewFeature};
 use schema_connector::{ConnectorError, ConnectorHost, IntrospectionResult, Namespaces, SchemaConnector};
 use std::{