Fix resolver crash and handling name limits

[rcaselles]

What does this PR do?

This PR addresses issue #9020. It attempts to resolve the problem by dividing the data into smaller chunks and then combining them using a XOR operation. However, I am open to suggestions if there is a more optimal method to accomplish this.

Additionally, I have standardized the maximum name length across both the parser and the init command to align with npm's requirements. According to the npm documentation (https://docs.npmjs.com/cli/v10/configuring-npm/package-json#name), the maximum length for a package name is 214 characters. This standardization was necessary but had not been previously included in our implementation (in both package_json.zig and init_command.zig)

To further enhance usability, I've implemented retries for cases where the name length does not meet this limit. This should help ensure that users are able to correct the input without having to restart the process entirely.

How did you verify your code works?

I tested with the provided package.json, and different new project configs

[Jarred-Sumner]

Thank you for this, but this PR is much complicated for what seems like a very unusual edgecase.

• The comments feel very much like prompting an LLM
• This adds errors which shouldn't error
• This adds an unnecessary temporary memory allocation
• Uses page_allocator which would should not be used outside of tests