refactor(napi/parser): move generated deserializer files

[overlookmotel]

Pure refactor. Move generated deserializer files for napi/parser into a generated/deserialize directory. This is to make room for more generated files (e.g. visitor, more specialized deserializers), without the number of file in root of the package exploding.

[overlookmotel]

• perf(napi/parser): lazy load raw transfer deserializers #10482
• refactor(napi/parser): move generated deserializer files #10481 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[overlookmotel]

@Boshen Will the release scripts include files in generated directory in the NPM package? I can't figure out what the Github actions for releases are doing, and for some reason can't get the pnpm napi commands in them to run locally in order to test it.

[graphite-app]

Merge activity

• Apr 19, 10:12 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Apr 19, 2:33 PM UTC: The Graphite merge queue couldn't merge this PR because it timed out.
• Apr 29, 5:43 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Apr 29, 5:54 AM EDT: overlookmotel added this pull request to the Graphite merge queue.
• Apr 29, 5:54 AM EDT: Merged by the Graphite merge queue.

[Boshen]

Conflict.