Unexpected default maxBodyLength enforcement by follow-redirects

[mhassan1]

Describe the bug

As part of the upgrade of follow-redirects in #2689, a default maxBodyLength of 10MB began to be enforced (previously, there was no request payload limit). There are a few issues with this:

1. The default limit is not mentioned in the axios documentation
2. This change in defaults is not included as a breaking change in the axios changelog
3. The default is unlimited when maxRedirects = 0

To Reproduce

axios.post('/size', 'x'.repeat(1e8))
// -> Error: Request body larger than maxBodyLength limit

axios.post('/size', 'x'.repeat(1e8), { maxBodyLength: -1 })
// -> Error: Request body larger than maxBodyLength limit

axios.post('/size', 'x'.repeat(1e8), { maxRedirects: 0 })
// -> OK

axios.post('/size', 'x'.repeat(1e8), { maxBodyLength: Infinity })
// -> OK

Expected behavior

The default maxBodyLength should be consistent and documented, regardless of the value of maxRedirects.

Environment

• Axios Version: 0.24.0
• Adapter: HTTP
• Browser: N/A
• Browser Version: N/A
• Node.js Version: 16.13.0
• OS: OS X 11.6
• Additional Library Versions: N/A

Additional context/Screenshots

This is related to #3786, although I don't think that PR goes far enough to correct the inconsistent behavior.

[mitsos1os]

This bug is still valid.

Axios only passes down maxBodyLength configuration to follow-redirects when it has a value greater than -1 here

This results to follow-redirects using its default 10mb limit set here, when axios default (which is supposed to be unlimited) -1 value used

There has to be a correction for the default case, where if axios limit is set to -1 then Infinity should be passed to follow-redirects to have similar behavior in its checking logic here