ci: add root level tasks to lage

[Saadnajmi]

Description of changes

We have some tasks that run per pacakge (build, lint, etc), and some that run at the workspace level (lint-lockfile, format because its way faster that way, etc. We didn't clearly delineate these two types of tasks and Lage would get confused when I tried to. So, I asked Claude to do it.

While here, also bump Yarn to 4.13.0 because i noticed that updated :)

Claudes summary of the changes below

Add root-level tasks to lage pipeline

Problem

Several repo-wide checks (format:check, lint-lockfile, check-publishing) were running as standalone CI steps outside of lage, or not running at all through lage's task scheduler.

Changes

package.json

• Added "." to workspaces so lage discovers the root package as a workspace, enabling root-only tasks
• Added "lint-lockfile": "lint-lockfile" script (required for lage to invoke it as a pipeline task)
• Removed scripts whose names collide with lage task/alias names (buildci, bundle, clean, lint, lint-package, test) — these caused infinite recursion because lage would invoke the script, which invoked lage again. Scripts that call lage but don't match a task name (lint-fix, lint-package-fix, build) are kept

lage.config.js → lage.config.mjs

• Converted to ESM
• Added three root-only pipeline tasks with cache: false (using **/* inputs at the repo root would OOM from hashing the entire monorepo): check-publishing, format:check, lint-lockfile
• Added repo-checks alias grouping the three root-only tasks — they run once at root instead of being spawned per-package
• Added repo-checks to buildci
• Removed format from the pipeline — sub-packages each have a format script, so lage format would spawn 80+ processes; yarn format at root already runs oxfmt over the whole repo in one shot
• Removed pr-check alias — unused and redundant (was a subset of buildci)
• Reorganized pipeline into labelled sections: per-package tasks, root-only tasks, pipeline aliases, worker tasks

.github/workflows/pr.yml

• Removed standalone Check formatting and Run lint-lockfile steps — both are now covered by buildci via repo-checks
• Changed yarn buildci → yarn lage buildci (root no longer has a buildci script)

Verification

CI should pass

Pull request checklist

This PR has considered (when applicable):

• Automated Tests
• Documentation and examples
• Keyboard Accessibility
• Voiceover
• Internationalization and Right-to-left Layouts

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1f50a05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[JasonVMo]

I think these should be dependencies rather than peer dependencies as this is an endpoint package. If these are peer dependencies these packages should be added as devDependencies.

[Saadnajmi]

I believe this is the output of lint-package-fix. I'll see what happened

[Saadnajmi]

Peer dependencies were enforced transitively all the way down to app packages. I updated the lint rule to check if the kitConfig is "app" and skip enforcing the lint in that case. I also marked tester-win32 and tester-win32-81 as private because https://www.npmjs.com/package/@fluentui-react-native/tester-win32?activeTab=versions has basically zero downloads. That has the side effect of also moving their versions to 0.1.0