Enriched API schema

[wemeetagain]

Enriched schema would definitely be nice to have, especially for POST requests. I think we would have to pull a pinned version of the beacon-API schema from github and then override each route based on operationId. This will become especially important if we want to generate a API docs page with redoc (or similar tooling).

Originally posted by @nflaig in #5970 (comment)

[wemeetagain]

One annoying thing is that this will blow up our bundle size. Current unpacked package size is 424K, the schema is 691K

[wemeetagain]

@nflaig
I think we can close this as wontfix unless you have any other ideas about this.

[nflaig]

This will become especially important if we want to generate a API docs page with redoc (or similar tooling).

do we want to do this? I think we are fine with just the beacon-api spec and the explorer we have local still provides an overview of other custom apis

We can still fetch the beacon-api spec json from github on demand and enrich the schema when you access /documentation path and cache it afterwards.

I personally don't really use the local explorer since I only use curl, so not sure it would be useful to anyone