chore(auth-server): add project.json for VSCode test explorer

[nshirley]

Because:

• fxa-auth-server had no project.json so it was invisible to the Nx project graph; getJestProjectsAsync() skips it and the VSCode Jest Test Explorer never showed its tests.

This commit:

• Adds packages/fxa-auth-server/project.json registering the package with Nx; the test-unit target uses @nx/jest:jest so getJestProjectsAsync() returns the jest config path, making tests discoverable in the explorer
• Adds displayName: 'fxa-auth-server' to jest.config.js so the explorer labels the project correctly

CI is unaffected — yarn test-unit still delegates to scripts/test-ci.sh.

Checklist

Put an x in the boxes that apply

• My commit is GPG signed.
• If applicable, I have modified or added tests which pass locally.
• I have added necessary documentation (if appropriate).
• I have verified that my changes render correctly in RTL (if appropriate).
• I have manually reviewed all AI generated code.

How to review (Optional)

• Key files/areas to focus on:
• Suggested review order:
• Risky or complex parts:

Screenshots (Optional)

Note

Worth calling out, this is ONLY for unit tests. Integration tests proved to be difficult because of test-server setup and may need to wait for that to be stripped out

Here's the VSCode extension able to discover the tests.

I hit a few quirks with the runner with this.

• You might need to reload the vscode instance, this can be done by opening the command pallet cmd+shift+p by default, and running Developer: Reload Window
• The first time running a test from the explorer might look like it's hanging, just check Test Results panel to see if it's processing. I'm not sure what this delay is, maybe something with nx happening in the background?
• When drilling down into tests, the explorer might not be able to discover tests for a module unless that module is open. So, don't just click the arrow, but click the module itself to open it in the editor
  • Before, not showing tests:
  • After, clicked module and open in editor:

Other information (Optional)

Any other information that is important to this pull request.

[Copilot]

Pull request overview

Registers packages/fxa-auth-server as an Nx project so Nx/Jest tooling (notably VSCode Jest Test Explorer via getJestProjectsAsync()) can discover and label its Jest configuration correctly.

Changes:

• Added packages/fxa-auth-server/project.json to define Nx targets, including a Jest-backed test-unit target.
• Added displayName: 'fxa-auth-server' to packages/fxa-auth-server/jest.config.js for clearer project labeling in Jest tooling.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
packages/fxa-auth-server/project.json	Registers fxa-auth-server with Nx and defines test-* targets (unit via @nx/jest:jest, others via run-commands).
packages/fxa-auth-server/jest.config.js	Adds displayName to improve test project labeling in Jest explorers/reporters.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

outputs is currently limited to the junit directory under artifacts/tests, but this target runs Jest and jest.config.js writes coverage to ../../artifacts/coverage/fxa-auth-server-jest when --coverage is enabled. With the current outputs, Nx caching/artifact tracking may miss the coverage directory, and the hard-coded path duplicates the project name. Consider either removing the explicit outputs (rely on defaults) or using placeholders and including the coverage output directory as well.

[nshirley]

Since this is currently only added so the vscode explorer can discover the tests, this isn't necessarily an issue. But, I'll remove the outputs and rely on the default for now