feat: rewrite toolbar reference page for new APIs

[Princesseuh]

Description (required)

Rewrite the toolbar api reference to match new APIs

Related issues & labels (optional)

withastro/astro#10665 & withastro/astro#10667 rework how to make dev toolbar APIs to make it easier to make apps

[vercel]

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

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Apr 24, 2024 0:26am

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
docs-i18n	⬜️ Ignored (Inspect)		Apr 24, 2024 0:26am

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	reference/dev-toolbar-app-reference.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

Just a few initial comments reading through the file diff here (because some of what's showing up as "new" isn't really new).

I will also do a review comparing both live docs and the deploy preview here, but just a few tiny things that stood out to me here!

[sarah11918]

OK! Looking great @Princesseuh ! See my commit above with some light touches (some of them outside of GitHub's editing area, so easier just to make directly going through the page) and confirm everything I did is correct...and desirable! Also a couple of questions/notes/confirmation left unresolved here! But, very close to good to go, I think!

[sarah11918]

OK! I made a commit to address those comments, and otherwise this is ready for your approval!

I'll be making a 4.7.0 branch and pointing these two PRs to them so that they are aware of each other. That will fix the failing link in the other one, and allow me to integrate the link on this page I added in the other PR.

[sarah11918]

Merging into 4.7.0 branch for final checks!