update dependencies to latest

[zachwaffle4]

Description

This fixes a tsc error I was getting and also lets us not pin the Satteri version in pnpm-workspace

This also switches pnpm from packageManager to devEngines.packageManager, because the latter supports version ranges and so we don't have to update that field every time pnpm releases an update :)

Closes #228

Meta

Merge checklist:

• Pull Request title is short, imperative summary of proposed changes
• The description documents the what and why, including events that led to this PR
• Pull Request has been linted and formatted and follows the styleguide

[github-actions]

🌐 Preview URL: https://pr-237-frcsoftware.frcsoftware.workers.dev

[Copilot]

🟢 Approval recommended

Changes are limited to dependency/config updates and the repo’s CI workflows include build + lint checks on pull requests.

Pull request overview

Updates the project’s dependency set and pnpm configuration to resolve a TypeScript compile error and remove the temporary workspace-level pin on satteri (per #228).

Changes:

• Bumped key Astro/Starlight ecosystem packages and dev tooling (including TypeScript ESLint and @types/node).
• Removed the pnpm workspace overrides block that forced satteri to a specific range, and refreshed the lockfile accordingly.
• Updated the declared pnpm version via packageManager in package.json.

File summaries

File	Description
pnpm-workspace.yaml	Removes temporary pnpm override/exclude configuration (including the satteri pin).
pnpm-lock.yaml	Refreshes the lockfile to reflect the updated dependency graph and removal of overrides.
package.json	Updates packageManager and bumps direct dependencies/devDependencies to newer versions.

Review details

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

• Files reviewed: 2/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟡 Changes recommended

The updated pnpm-lock.yaml appears to be two concatenated YAML documents (duplicate ---), which is likely invalid for pnpm and would break installs/CI.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

• Files reviewed: 2/3 changed files
• Comments generated: 3
• Review effort level: Lite