Raise the bodyLimit to 50MB from 1MB

[NullVoxPopuli]

In this PR:

• Bug fix (non-breaking change which fixes an issue)

Issues reference:

Related: #366

I have a library that is 3.3MB right now, and I kinda "arbitrarily" chose 50MB, but I figure if some build assets could include images, it may be good to bump further.

Any larger than that though, and... folks should probably statically host those images somewhere.

---

Alternatively, I see (in #366) there is a BODY_LIMIT environment variable -- must be a fastify thing 😅

I was not able to find that in fastify's docs though?

Checklist:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

• Have you lint your code with pnpm lint locally prior to submission?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran build with pnpm build of your changes locally?
• Have you successfully ran tests with pnpm test of your changes locally?
  • aside from the minio test -- address already in use error
• Have you commit using Conventional Commits?

[fox1t]

You can find all of the env vars supported by remote cache here. https://ducktors.github.io/turborepo-remote-cache/environment-variables

Btw I think this is a sane change and we are going to merge this.

[matteovivona]

🎉 This PR is included in version 2.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[matteovivona]

@all-contributors add @NullVoxPopuli on code

[matteovivona]

Related to this issue #323

[allcontributors]

@matteovivona

I've put up a pull request to add @NullVoxPopuli! 🎉