refactor: deprecates params and search params contexts

[jacobsfletch]

As described in #9576, the SearchParamsProvider can become stale when navigating routes and relying on search params during initial render. This is because this context, along with the ParamsProvider, is duplicative to the internal lifecycle of useSearchParams and useParams from next/navigation– but always one render behind. Instead, we need to use the hooks directly from next/navigation as described in the jsdocs. This will also remove any abstraction over top the web standard for URLSearchParams.

For this reason, these providers and their corresponding hooks have been marked with the deprecated flag and will continue to behave as they do now, but will be removed in the next major release. This PR replaces all internal reliance on these hooks with next/navigation as suggested, except for the useParams hook, which was never used in the first place.

'use client'
- import { useSearchParams } from '@payloadcms/ui'
+ import { useSearchParams } from 'next/navigation'
+ import { parseSearchParams } from '@payloadcms/ui'

export function MyClientComponent() {
- const { searchParams } = useSearchParams()
+ const searchParams = useSearchParams()
+ const parsedParams = parseSearchParams(searchParams)

  // ...
}

MyClientComponent.tsx

[github-actions]

🚀 This is included in version v3.3.0