(router): remove not-found param from web url on not found pages

[marklawlor]

Why

ENG-10875

Remove the not-found param from web URLs

How

When converting State->Path we use matchDeepDynamicRouteName to extract catch-all route param names, and ensure these are not serialised in the URL.

While +not-found had the correct route pattern, our logic is going off the route name which does match the regex

I added a special condition instead of updating the regex.

expo/packages/expo-router/src/matchers.tsx

Lines 9 to 11 in 3e25547

	export function matchDeepDynamicRouteName(name: string): string | undefined {
	return name.match(/^\[\.\.\.([^/]+?)\]$/)?.[1];
	}

Test Plan

We had an existing test giving a false positive due to an incorrect pattern for the +not-found route

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[EvanBacon]

Does this work with nested not-found, e.g. foo/+not-found?

[marklawlor]

Fix this and updated the PR with extra tests.

I added a new matcher getPathnameWithParams that allows you to assert what the pathname is with the query parameters.

[marklawlor]

@EvanBacon While working on this PR I noticed that global parameters for catchall routes where not being properly decoded. Currently the parameters for catch all routes are joined to a comma separated list. That was causing these new tests to fail

I fixed the issue and updated the other affected tests. We had tests around this, but they were ineffective as they simply tested single values for catch all routes. I've updated these tests to use a variety of single and multiple values.