[Docs] Updates docs to use astro/cloudflare pages

[andrewfulton9]

Reference Issues or PRs

Closes #11

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[killua156]

LGTM — clean Yarn→npm + TS docs migration, CI green. Nit: README doesn't mention the new typecheck script.

[andrewfulton9]

Must be convert to Astro docs engine

[jbouder]

Closing in favor of #22, which builds directly on this work — same Astro + Starlight + Cloudflare Pages approach — rebased on current main and aligned with the docs setup the other packs have since converged on (nebi-pack, apps-pack, nebari-chat-pack): the @nebari/starlight shared theme plugin instead of a hand-copied token stylesheet, docs.yml with SHA-pinned actions, and the SITE/BASE defaults so a plain npm run build matches production. Thanks for the groundwork here.