@next/next/no-server-import-in-page ESLint rule throws on test files

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Tue Jun 23 12:58:10 UTC 2020
    Binaries:
      Node: 16.14.2
      npm: 8.5.0
      Yarn: 3.2.0
      pnpm: N/A
    Relevant packages:
      next: 12.1.6
      react: 18.1.0
      react-dom: 18.1.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

When a test file in the pages folder exists that imports next/server, the rule @next/next/no-server-import-in-page throws during next build.

Expected Behavior

Test files, either those in __tests__ or file.test.ts should be ignored for this rule

To Reproduce

package.json

    "@typescript-eslint/parser": "^5.25.0",
    "eslint": "^8.15.0",
    "eslint-config-next": "^12.1.6",
    "eslint-plugin-react": "^7.29.4",

.eslint.json

{
  "root": true,
  "extends": "next/core-web-vitals",
  "parser": "@typescript-eslint/parser"
}

Create a file at pages/__tests__/example.test.ts

import "jest";
import { NextRequest } from "next/server";

describe("example", () => {
  it("should pass", () => {});
});

Run next build or deploy to Vercel

[Shubhamchinda]

@Shubhamchinda are you planning to work on this or could I take it over?

@aboqasem Please take it.

[rikkit]

@Shubhamchinda go for it