feat: add technical docs

[kallebysantos]

Warning

Working in progress, I'll be using the GitHub integrated markdown editor in order to attach useful images

• Commits must be clean up/rebase before switch to review

---

What kind of change does this PR introduce?

docs update

What is the current behavior?

Missing technical relevant information about Edge Runtime as well upstream Deno.

What is the new behavior?

This PR solves #537 by adding more relevant docs about all internal crates and the whole project structure

starting from the ones I really understand well: ai

[kallebysantos]

Hi @nyannyacha, is possible to turn off ci pipeline for this specific PR while its in draft? So we can avoid waste computer time on it.

Or may you have any recommendations for how should I do attach images to .md files? I'm planning to draw some illustrations for it.

[nyannyacha]

Hi @nyannyacha, is possible to turn off ci pipeline for this specific PR while its in draft? So we can avoid waste computer time on it.

Opened a PR for it 😋 #544
But @laktek is coming back from vacation tomorrow, so it probably won't get merged until then.

Or may you have any recommendations for how should I do attach images to .md files? I'm planning to draw some illustrations for it.

When I wanted to reference images in Markdown, I placed the images in the assets directory.
You can see how the asset is referenced here: https://github.com/supabase/edge-runtime/blob/develop/DEVELOPERS.md?plain=1#L89