fix: Use BODY_LIMIT when creating app

[jgoz]

In this PR:

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

The BODY_LIMIT env variable was being used in the content type parser, but not when creating the fastify app. This meant the practical body limit could not be raised past 50MB.

This PR uses the BODY_LIMIT var for both values.

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 successfully ran build with pnpm build of your changes locally?
• Have you successfully ran tests with pnpm test of your changes locally?
• Have you commit using Conventional Commits?

[jgoz]

@matteovivona Does this change make sense?

[jakeinflab]

I agree with this change. We are running a very large project where our cache size exceeds 50MB, resulting in issues with loading the cache. Could you please review this change?
@matteovivona @jgoz

[matteovivona]

@jgoz thank you for your PR! It makes sense.
Could you also update the documentation with this new variable? I would really appreciate it!

[matteovivona]

@all-contributors please add @jgoz for code and doc

[allcontributors]

@matteovivona

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

[fox1t]

LGTM after doc change. Thanks for the PR.

[jgoz]

@fox1t @matteovivona The docs already have this variable listed, it just wasn't being used in this spot.

[matteovivona]

🎉 This PR is included in version 2.2.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀