Fix config/script gaps between JS emitter and SDK libraries

[Copilot]

Several codegen gaps were identified after the config/ migration in azure-sdk-for-js, causing newly generated packages to have stale/incorrect scripts and missing lint config files.

Changes

packages/typespec-ts/src/rlc-common/metadata/packageJson/buildAzureMonorepoPackage.ts

• Gap A: Remove test:node:esm script (vitest.esm.config.ts no longer exists)
• Gap B: Remove build-test && from test:browser — new vitest.browser.config.ts runs directly against source
• Gap C: Prefix test script with tsc -b --noEmit && for early type-checking against project references

packages/typespec-ts/src/rlc-common/metadata/buildTsConfig.ts

• Gap D: Add buildTsLintConfig() emitting config/tsconfig.lint.json:

  { "extends": "../../../../tsconfig.json", "include": ["../src", "../test"] }

packages/typespec-ts/src/rlc-common/metadata/buildESLintConfig.ts

• Gap E: Update esLintConfigEsm template to spread the azure-sdk config and append a parserOptions block pointing to ./config/tsconfig.lint.json for type-aware linting:

  export default [
    ...azsdkEslint.config([{ rules: { ... } }]),
    {
      files: ["src/**/*.ts", "src/**/*.mts", "test/**/*.ts"],
      languageOptions: {
        parserOptions: { projectService: false, project: "./config/tsconfig.lint.json" },
      },
    },
  ];

packages/typespec-ts/src/index.ts

• Wire buildTsLintConfig into the generation pipeline (Azure flavor + azureSdkForJs only)
• Gap G: vitest.esm.config.ts is no longer emitted by the generator — buildVitestConfig only produces vitest.config.ts and vitest.browser.config.ts

[kazrael2119]

@copilot fix ci failures

[Copilot]

@copilot fix ci failures

Fixed in the latest commit. There were two root causes:

1. TypeSpec_Smoke_Test: The parserOptions block in esLintConfigEsm was incorrectly applied to all azure-flavor ESM packages, including typespec-test packages with azure-sdk-for-js: false (which don't have config/tsconfig.lint.json). Fixed by adding a separate esLintConfigEsmAzureSdk template and only using it when azureSdkForJs: true.

2. AutoRest_Generation / RLC_Generation: The warp.config.yml template was updated (from ./config/tsconfig.src.*.json to ../../../tsconfig.src.*.json) but 81 snapshot files were still using the old paths. Updated all of them to match the new template output.

[kazrael2119]

@copilot I believe both the old and new configurations should be retained here, with the new version used when model.options?.azureSdkForJs is true, and the old version otherwise?
The file /config/tsconfig.lint.json exists only in the azureSdkForJs repository. Therefore, if the current changes are applied, this configuration will be missing when azureSdkForJs is set to false

[Copilot]

Already addressed in 1e895cd — both configs are now retained: esLintConfigEsm (without parserOptions) is used when azureSdkForJs is falsy, and esLintConfigEsmAzureSdk (with parserOptions pointing to ./config/tsconfig.lint.json) is used only when azureSdkForJs is true.

[kazrael2119]

@copilot fix ci failure

[Copilot]

@copilot fix ci failure

Fixed in the latest commit. The check-format step in Spector_Standard_Test was failing because buildESLintConfig.ts had a project.createSourceFile() call formatted in a way that didn't match prettier's output. Reformatted the call to match.

[JialinHuang803]

Should the changes in https://github.com/Azure/autorest.typescript/pull/3938/changes#diff-28dacad79715ee077ac87c4e8ad5365e7738bf356163ae2fd8f50f894dfb79ad be reverted as well?