Use upstream graphql_ppx, upgrade ppxlib

[Firobe]

Closes #11081

This:

• removes the graphql_ppx and ppx_deriving_yojson submodules
• upgrades ppxlib and removes old PPX tooling
• pins graphql_ppx to upstream's master branch (until there is a release for it)
• fixes broken PPXs across the code base broken by the ppxlib upgrade
  • ppx_optcomp (actually, remove ppx_optcomp actually, no): Merge upstream v14.3 for recent ppxlib compatibility ppx_optcomp#8
  • ppx_version: Use latest ppxlib AST o1-labs/ppx_version#37
  • ppx_coda
  • snarky's PPX (both for compatible and develop): Upgrade for latest ppxlib (coda branch) o1-labs/snarky#633 for develop, compatible no PR needed
  • ppx_util
  • ppx_register_event
  • crypto_params gen
  • mina_base gen
  • gen_values
• fixes GraphQL queries and schemas broken by the upgrade
  • replace deprecated directives by new ones (bsDecoder -> ppxCustom, ...)
  • group decoders and encoders into modules that can be fed to ppxCustom (when one way is unavailable, failwith)
  • adapt interface around generated modules (using extend? by modifying graphql_ppx?)
  • fix CLI
  • fix Rosetta
  • fix Archiver
  • fix integration tests
  • fix frontend? doesn't seem necessary
• fixes breakage due do js_of_ocaml upgrade
• fixes conflict with compatbile
• adds a config file to configure the GraphQL ppx globally? Will be done in another PR, once Allow list expansion in preprocessor arguments ocaml/dune#5820 has landed in dune

[Firobe]

Note: the new upstream graphql_ppx cannot be mixed with ppx_optcomp due to their nature. Also, ppx_jane implicitly contains ppx_optcomp, so when using graphql_ppx, ppx_jane must be deconstructed into only its needed ppxs.

[Firobe]

PPXs seem fixed, now fixing the GraphQL interface/queries

[Firobe]

This PR is more or less now ready for review! I still want to see if I can use a config file to factorize the ppx parameters, but that can be done in parallel with reviewing. It uses the upstream graphql_ppx with no modification, and adapts the codebase around it. CI is green (except an unrelated failure).

There is no develop PR yet, but it will be in the same vein.
Companion PR: #11159

I expect we will want to customize graphql_ppx to avoid some of the work-arounds I've used, but I believe we can start from this proof-of-concept and we should merge the ppxlib etc. update sooner rather than later. No changes to the old custom graphql_ppx were ported for now, as most do not seem necessary, but feel free to tell me otherwise.

The changes are separated in atomic commits, and I suggest to start a review with commit 93f38b6, which is representative of the rest.

[mimoo]

random thought looking at this file. I was investigating adding pins here instead of our setup script, but modifying this file by hand seems hard (no documentation on how to do it that I could find) and error prone (as it is supposed to be a machine generated file).

It would be nice to be able to list all the dependencies, all the pins, and the OCaml version we use, in a single .toml or .json file (similar to a Cargo.toml in Rust)

[Firobe]

Yeah, I'd really like to add all pins here in the long term, and potentially get rid of submodules. I'd argue that modifying this file by hand is feasible (this is what I've been doing thus far), but we can talk about generating it from something else.

We can have that discussion in this issue: #10982

[Firobe]

So, it seems factorizing the graphql_ppx arguments cannot be done yet because

1. The bsconfig.json file way is not working
2. Dune cannot expand lists in ppx parameters yet.

I have a PR to fix 2 in dune (ocaml/dune#5820), and I'll do the factorization in a different PR, once the dune change has landed in a release.