Update Turbopack production test manifest

[vercel-release-bot]

This auto-generated PR updates the production integration test manifest used when testing Turbopack.

[ijjk]

Failing test suites

Commit: f655f3f398bb30740bba25d1bb99f7b1d0d7086b

pnpm test-start-turbo test/production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts (turbopack)

• app-dir - server-action-period-hash-custom-key > should have different manifest if the encryption key from process env is same

Expand output

● app-dir - server-action-period-hash-custom-key › should have different manifest if the encryption key from process env is same

expect(received).toEqual(expected) // deep equality

- Expected  - 1
+ Received  + 1

  Array [
-   "81e52064757b1e34218e39676e6c7b2e5308976d",
    "8f1c262d3399e85740ee631e51483f7b9e199431",
+   "81e52064757b1e34218e39676e6c7b2e5308976d",
  ]

  16 |
  17 |   if (equal) {
> 18 |     expect(keysA).toEqual(keysB)
     |                   ^
  19 |   } else {
  20 |     expect(keysA).not.toEqual(keysB)
  21 |   }

  at toEqual (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:18:19)
  at Object.compareServerActionManifestKeys (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:56:5)

Read more about building and testing Next.js in contributing.md.