fix(deps): upgrade many deps

[boneskull]

Upgrades @astrojs/starlight, astro, astro-embed, markdownlint-cli2 and typescript to latest versions.

Moved all dependencies to devDependencies, since there are no actual dependencies.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	astro-embed@​0.7.2 ⏵ 0.9.2	+6		+5	+4
	@​astrojs/​check@​0.7.0 ⏵ 0.9.5			+15	+9
	@​astrojs/​starlight@​0.24.4 ⏵ 0.36.2			+1	+3
	astro@​4.11.1 ⏵ 5.16.0		+50		+1
	markdownlint-cli2@​0.14.0 ⏵ 0.19.0	+1		+1	+6

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		GitHub dependency: npm volar-service-emmet depends on ramya-rao-a/css-parser Dependency: @emmetio/css-parser@ramya-rao-a/css-parser@#vscode Location: Package overview From: package-lock.json → npm/@astrojs/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[boneskull]

• Updated @astrojs/check to mitigate the problem noted in the nastygram
• Fixed tsconfig.json with settings recommended by Astro
• Fixed how we're checking types in CI

[boneskull]

Having trouble reproducing the failure locally. hmm.