fix(nextjs): Handle pathname being passed in object in instrumentServer (#5782)

In nextjs version 12.2.6, the signature of `findPageComponents` which we wrap in `instrumentServer` changed[1], from accepting individual parameters to accepting an options object. This changes our wrapping to accommodate that, and as a result fixes transactions started by `instrumentServer` being parameterized as `[ object Object ]`. For backwards compatibility with older versions of next, individual parameters also continue to be accepted.

[1] vercel/next.js@5f95b6b#diff-2b8e3503c1bebf856610a5551d9c5996435b99f45db389d4eeac1b671518875eR242-R248

Author: lobsterkatie

packages/nextjs/src/utils/instrumentServer.ts

@@ -317,14 +317,23 @@ function makeWrappedMethodForGettingParameterizedPath(
   origMethod: ApiPageEnsurer | PageComponentFinder,
 ): WrappedApiPageEnsurer | WrappedPageComponentFinder {
   // eslint-disable-next-line @typescript-eslint/no-explicit-any
-  const wrappedMethod = async function (this: Server, parameterizedPath: string, ...args: any[]): Promise<any> {
+  const wrappedMethod = async function (
+    this: Server,
+    parameterizedPath:
+      | string // `ensureAPIPage`, `findPageComponents` before nextjs 12.2.6
+      | { pathname: string }, // `findPageComponents` from nextjs 12.2.6 onward
+    ...args: any[]
+  ): Promise<any> {
     const transaction = getActiveTransaction();
 
     // replace specific URL with parameterized version
     if (transaction && transaction.metadata.requestPath) {
       const origPath = transaction.metadata.requestPath;
-      const newName = transaction.name.replace(origPath, parameterizedPath);
-      transaction.setName(newName, 'route');
+      const newPath = typeof parameterizedPath === 'string' ? parameterizedPath : parameterizedPath.pathname;
+      if (newPath) {
+        const newName = transaction.name.replace(origPath, newPath);
+        transaction.setName(newName, 'route');
+      }
     }
 
     return origMethod.call(this, parameterizedPath, ...args);