chore(ci): Update Next.js canary testing (#17939)

next@canary now resolves to next 16 which is why we need to update the
testing strategy here

Author: chargome

.github/workflows/canary.yml

@@ -76,11 +76,8 @@ jobs:
             build-command: 'test:build-canary'
             label: 'create-react-app (canary)'
           - test-application: 'nextjs-app-dir'
-            build-command: 'test:build-canary'
-            label: 'nextjs-app-dir (canary)'
-          - test-application: 'nextjs-app-dir'
-            build-command: 'test:build-latest'
-            label: 'nextjs-app-dir (latest)'
+            build-command: 'test:build-15'
+            label: 'nextjs-app-dir (next@15)'
           - test-application: 'nextjs-13'
             build-command: 'test:build-latest'
             label: 'nextjs-13 (latest)'
@@ -90,12 +87,15 @@ jobs:
           - test-application: 'nextjs-14'
             build-command: 'test:build-latest'
             label: 'nextjs-14 (latest)'
-          - test-application: 'nextjs-15'
-            build-command: 'test:build-canary'
-            label: 'nextjs-15 (canary)'
           - test-application: 'nextjs-15'
             build-command: 'test:build-latest'
             label: 'nextjs-15 (latest)'
+          - test-application: 'nextjs-16'
+            build-command: 'test:build-canary'
+            label: 'nextjs-16 (canary)'
+          - test-application: 'nextjs-16'
+            build-command: 'test:build-canary-webpack'
+            label: 'nextjs-16 (canary-webpack)'
           - test-application: 'nextjs-turbo'
             build-command: 'test:build-canary'
             label: 'nextjs-turbo (canary)'