feat(build): reduce boilerplate duplication in material.angular.io folder

[alexeagle]

Feature Description

Since the github.com/angular/material.angular.io repo was brought into this repo in a subfolder, it brought its root files with it:

• A separate yarn workspace
• .bazelversion (7.3) which differs from the root (5.0)
• Other Bazel files defining the repository root
• Linter/formatter configurations

We may want to brainstorm a sequencing of infra changes to improve this, especially if engineers need to make commits that affect files both inside and outside this subdirectory, or need a functional Bazel dependency graph so targets can refer to others across that boundary.

Note that GHA workflows were merged in #30288 as a beginning to solving this issue.

Use Case

No response