Docs UI update

[ZYJLiu]

1. Add Tabs/Tab component
   

Example usage on developer-content md files:

<!-- prettier-ignore -->
<Tabs groupId="language" items={['Rust', 'Typescript', 'Java']}>
<Tab value="Rust">Rust 1</Tab>
<Tab value="Typescript">Typescript 1</Tab>
<Tab value="Java">Java</Tab>
</Tabs>

<!-- prettier-ignore -->
<Tabs groupId="language" items={['Rust', 'Typescript', 'Go']}>
<Tab value="Rust">Rust 2</Tab>
<Tab value="Typescript">Typescript 2</Tab>
<Tab value="Go">Go</Tab>
</Tabs>

<!-- prettier-ignore -->
<Tabs groupId="package-managers" items={['pnpm', 'npm', 'yarn']}>
<Tab value="pnpm">pnpm 1</Tab> 
<Tab value="npm">npm 1</Tab>
<Tab value="yarn">yarn 1</Tab> 
</Tabs>

<!-- prettier-ignore -->
<Tabs groupId="package-managers" items={['pnpm', 'npm', 'yarn']}>
<Tab value="pnpm">pnpm 2</Tab> 
<Tab value="npm">npm 2</Tab>
<Tab value="yarn">yarn 2</Tab> 
</Tabs>

2. Add Accordion/AccordionItem component

Example usage on developer-content md files:

  <Accordion>
  <AccordionItem title="Hello">
  
  ```ts
  console.log("hello");
  ```
  
  </AccordionItem>
  <AccordionItem title="World">
  
  ```rs
  println!("world");
  ```
  
  </AccordionItem>
  </Accordion>

3. Update docs codeblock UI with svgs icons in header
   

4. Add lightmode color to docs components/codeblock
   
   
   

5. Update docs scrollbar to only appear on hover
   

6. Fix doc table of content bug where "SOL" gets converted to "SO"

7. Update Table of Contents "Edit Page" and "Scroll to Top" buttons
   

8. Add Stack Exchange to docs secondary nav
   

[vercel]

@ZYJLiu is attempting to deploy a commit to the Solana Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
solana-next-com	✅ Ready (Inspect)	Visit Preview	Aug 1, 2024 4:00pm

[nickfrosty]

great work here John! the new components will be a great addition to the site. better UX all around! :)

I just have the one concern about the regex fix for other languages. we need to find a different solution

[nickfrosty]

updating this regex to your suggesest change will break all translated content within the table of contents. and maybe prevent the site from building.

we need to find a different solution to solve the "trailing L" bug we are seeing

[nickfrosty]

same comment as above

[mikemaccana]

Please add the usage guidelines for the new components (you've already added them in the text of this PR) into CONTRIBUTING.md

[ZYJLiu]

Please add the usage guidelines for the new components (you've already added them in the text of this PR) into CONTRIBUTING.md

will add to developer-content, since that is where the components are used

[nickfrosty]

Great work on this John. I think people are going to really like these new UX improvements

captured and will be accomplished in the dev content repo

[nickfrosty]

Please add the usage guidelines for the new components (you've already added them in the text of this PR) into CONTRIBUTING.md

added tracking issue on dev content: solana-foundation/developer-content#288

[mikemaccana]

BTW @ZYJLiu you can use \p{Letter} and \p{Number} to make the unicode bits more obvious. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Regular_expressions/Unicode_character_class_escape