Add failing test for client-side router filtering

[crisvergara]

Tests for #47486 . Illustrates a collision that causes a hard navigation for a random page based on behavior we see in our private repository.

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: e73139c

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[ijjk]

Failing test suites

Commit: e73139c

pnpm test test/unit/create-client-router-filter.test.ts

• createClientRouterFilter > creates a filter that does not collide with wildly different path names

Expand output

● createClientRouterFilter › creates a filter that does not collide with wildly different path names

expect(received).toBe(expected) // Object.is equality

Expected: false
Received: true

  25 |         '/all-hardcovers/no-one-can-know-1511?category=current-features'
  26 |       )
> 27 |     ).toBe(false)
     |       ^
  28 |   })
  29 | })
  30 |

  at Object.toBe (unit/create-client-router-filter.test.ts:27:7)

Read more about building and testing Next.js in contributing.md.

[ijjk]

Thanks for opening this test case, included it in #60542