feat: use the new api proxy and improve embed shortcode

[hugomrdias]

This PR adds:

• Support for the new API proxy
  • The proxy will handle all the external resources, caching and transforming data to our needs
  • New repo with the Proxy will be published asap
• Code coverage and CI status is now handled by the proxy
• Code blocks from github are now support in the embed shortcode using the Proxy
• Code blocks with title or symbols have permalinks

{{<embed src="github:filecoin-project/specs-actors/actors/builtin/paych/paych_actor.go" lang="go" symbol="resolveAccount" title="Payment actor - Resolve Account">}}

• Code blocks from github have links to the github source page
  {{<embed src="github:filecoin-project/specs-actors/actors/builtin/paych/paych_actor.go" lang="go" symbol="resolveAccount">}}

• All Hugo Modules removed except the theme

No more codecov timeouts or go modules errors in the CI 🥳. The Proxy server should always keep data cached but fresh.

[olizilla]

Some VS Code plugin insists on adding the h1 from this doc to the ToC... I had to turn it off locally. I don't think we want it in the ToC.

[olizilla]

This is great! It can go in as is. A couple of suggestions

1. UI nit: Can we have the UI for code examples match the look of figures, by adding a subtle border and reducing the font size a little.

vs

2: UX nit... If the src attribute of the embed shortcode was just the github url, authors could copy and paste from their browser url bar when adding new embeds, and the markdown would more explicilty show what it was refering to.

{{<embed src="github:filecoin-project/specs-actors/actors/builtin/cron/cron_actor.go"  lang="go">}}
# vs
{{<embed src="https://github.com/filecoin-project/specs-actors/blob/master/actors/builtin/cron/cron_actor.go"  lang="go">}}

it seems nice to have the source code be a little less tied to the details of how the shortcode is currently implemented.

[hugomrdias]

1. 100% next PR will normalise those boxes and permalinks
2. the first version was exactly like that, but i wanted to take out the git ref (the shortcode supports ref="hash") so we can release with pinned tags instead of just master. Maybe im overthinking what do you think ?

Thinking about it now, each release will have the master version at the time of the CI run maybe we don't need this.... To give you more context im thinking about building history/versioning based in the Github Releases and IPFS deploys.

[olizilla]

Oh nice, i see. Well yes, as you said, I think you could use the github URL and the api could give the permalink to the latest commit at build time that the code snippet was pulled from.

If an author wants to link to a specific commit that never changes, they can just use the URL for that commit on github.

[hugomrdias]

the api could give the permalink to the latest commit at build time that the code snippet was pulled from.

Ah nice thats even better, didnt think about that. 💚 you are the best @olizilla

[hugomrdias]

btw 34s npm run build in the CI 🥳

[yiannisbot]

This is fantastic @hugomrdias!!