Support Oxc as an Alternative to ESLint for TypeScript Projects

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

As the TypeScript ecosystem evolves, the default linting and formatting stack used by Aspire is starting to feel outdated. While ESLint has served the community well for many years, newer tools like Oxc are quickly gaining adoption thanks to their significantly better performance, lower resource usage, and modern architecture.

With the release and growing adoption of TypeScript 7, many new projects are already choosing Oxc as their primary tooling instead of the traditional ESLint + Prettier combination. Currently, Aspire only scaffolds projects using the traditional stack, leaving developers to manually replace it afterward.

### Describe the solution you'd like

When running `aspire new`, provide an option to choose the linting/formatting stack during project creation

```
Which code quality tool would you like to use?

○ ESLint + Prettier
○ Oxc
```
This keeps Aspire flexible while allowing developers to adopt newer tooling without additional setup.

### Why this would be valuable
Much faster linting and formatting compared to the traditional ESLint + Prettier workflow.
Lower resource consumption, making development smoother on both local machines and CI.
Single toolchain for linting, formatting, parsing, and additional code quality features.
Rapid ecosystem adoption, especially in modern TypeScript projects.
Gives developers the freedom to choose the tooling that best fits their workflow without removing support for ESLint.

### Additional context

Oxc has matured into a production-ready toolchain that is seeing increasing adoption across the TypeScript ecosystem due to its speed and excellent developer experience.

I'm not suggesting removing ESLint support—only adding Oxc as a first-class alternative when scaffolding new TypeScript projects. This would help keep Aspire aligned with the direction many modern TypeScript projects are taking while remaining fully backward compatible.

Start with the `aspire new` scaffolding flow and its existing ESLint + Prettier setup for TypeScript projects. Run the project creation command to observe how options are presented and applied. Done means users can choose ESLint + Prettier or Oxc, while existing ESLint scaffolding remains available.

Written by the indexing model from the issue text.