Port technical blogs into our docs

[stevenli27]

Right now a lot of our technical features are only mentioned in our blog posts which are not easily accessible for new developers.

The blogs themselves also cater to a different audience and can be streamlined to only include the technical information for our docs.

The following blog posts should be ported over and turned into docs:

P0: These should be added under the bonsai section of our docs

Continuations: https://www.risczero.com/news/continuations Stark - Snark: https://www.risczero.com/news/on-chain-verification (Also highlight our existing sepolia groth16 contract)

P1: These can be added under the resources section of our docs Zeth: https://www.risczero.com/news/zeth-release Smartcore: https://www.risczero.com/news/rust-but-verify

[tzerrell]

A related issue for the continuations part: https://github.com/risc0/risc0/issues/1071

[stevenli27]

Would be really great to get some info regarding stark-snark / our sepolia verifier into our docs before dev connect

[nahoc]

@stevenli27 @tzerrell can this issue be closed now?

[tzerrell]

Probably ok to close, but I'm not very involved in directing our documentation these days, so @stevenli27 might be a better person to answer. I'm specifically not sure what judgement call to make for things like "are the existing zeth docs sufficient?"