What changed?

In this PR, we've:

1. fully removed react-syntax-highlighter and replaced it with a custom rehype plugin built on top of shiki.
2. all syntax highlighting is now computed server-side
3. line numbers are generated using special CSS, and bash/shell uses $ and > instead of line numbers
4. the order of the example json is now sorted to match the order that they appear in the API reference (this enhances readability, and hovering over property keys don't cause the code snippet scroll-area to jump all over the place).

Why make this change?

• react-syntax-highlighter is heavyweight, and requires a lot of work to make it dynamic, so that the initial JS is small. shiki ensures that every language and theme is dynamically loaded
• the customization options in react-syntax-highlighter is limited, requiring us to implement only a single color scheme, whereas shiki allows us to swap between a number of built-in themes, as well as enable providing custom TextMate theme files.
• light-mode and dark-mode are handled by shiki out-of-the-box, letting us apply the themes via CSS variables rather than using javascript. this ensures that no hydration failures occur and the theme is loaded before the DOM is ready.
• with shiki, we can offload syntax highlighting to occur on the server-side, significantly reducing the runtime burden from the client side
• we now have the option to implement several shiki transformers as well as twoslash for more interactive and rich code snippets

Why is this PR so large?

• implemented custom rehype plugin, which required bumping up our dependency of unified from 2 -> 3, in addition to a few other util packages
• in order to support server-side code snippets, i've introduced a major refactor of resolver.ts which now outputs safely serializable JSON, which required touching a bunch of places where the data structure is consumed.
• by moving syntax highlighting to the server-side, we actually significantly increase the size of the JSON payload b/c we are passing back the HAST for each code snippet. to reduce the payload size, i've went ahead and removed duplicate content, such as the unresolved api from the server. This required removing usage of pathResolver from the frontend, so I had to replicate the functionality using the new resolved data structure

What's next?

• add shiki transformers
• add twoslash integration for hoverable json property descriptions
• improve handling the HAST (currently, the HAST is turned in the JSX and we're parsing the JSX in CodeBlock/CodeBlocks. Instead, this should be parsed in the rehype step)

Before:

After:

Before:

After:

Before:

After:

Before:

After: