fix(ci): resolve Next.js 16 CI failures for starter example

Pin @wordpress/block-library to exact 9.10.0 to prevent SCSS import
breakage in E2E tests, add --webpack flag to bundle analysis build
for Turbopack compatibility, and drop Node 18 from E2E matrix to
match engines requirement.

Author: josephfusco

.github/workflows/e2e-next-faustwp-example.yml

@@ -14,7 +14,7 @@ jobs:
       PR_BRANCH: ${{github.event.pull_request.head.ref}}
     strategy:
       matrix:
-        node: ['18', '20', '22']
+        node: ['20', '22']
     defaults:
       run:
         working-directory: ./

.github/workflows/nextjs-bundle-analysis.yml

@@ -79,7 +79,7 @@ jobs:
 
       - name: Build Next.js example app
         working-directory: ${{ matrix.next-dir }}
-        run: npm run build
+        run: npm run build -- --webpack
 
       # Here's the first place where next-bundle-analysis' own script is used
       # This step pulls the raw bundle stats for the current bundle

examples/next/faustwp-getting-started/package.json

@@ -14,7 +14,7 @@
 		"@faustwp/cli": "^3.3.6",
 		"@faustwp/core": "^3.3.6",
 		"@wordpress/base-styles": "^6.15.0",
-		"@wordpress/block-library": "^9.10.0",
+		"@wordpress/block-library": "9.10.0",
 		"classnames": "^2.5.1",
 		"graphql": "^16.12.0",
 		"next": "^16.1.6",