Error after running jmeter test on Jenkins with multiple parameters passed via "-J" flag

### Expected behavior

No issues, test should be run successfully with multiple parameters passed via "-J" flag.

### Actual behavior

errorlevel=255

### Steps to reproduce the problem

I'm running jmeter test on windows based Jenkins node using next command (Windows batch command):

jmeter ^
-Jjmeter.save.saveservice.output_format=xml ^
-Jjmeter.save.saveservice.response_data=false ^
-Jjmeter.save.saveservice.samplerData=true ^
-Jjmeter.save.saveservice.requestHeaders=true ^
-Jjmeter.save.saveservice.url=true ^
-Jjmeter.save.saveservice.responseHeaders=true ^
-Jparam1=%param1% ^
…
-JparamN=%paramN% ^
-n -t "file.jmx" -l "%WORKSPACE%\Test%BUILD_NUMBER%.xml"

When number of params passed via flag "-J" exceeds 13, I'm getting "errorlevel=255" on Jenkins.
I was able to fix the issue by using "-D" flag instead of "-J" flag but it looks like there is a bug using "-J" flag.

### JMeter Version

5.5

### Java Version

1.8.0_362

### OS Version

Windows Server 2012 R2

Start by reproducing the Windows batch command on a Jenkins node with more than 13 -J parameters, using the reported JMeter 5.5 and Java 1.8. Compare the failing -J invocation with the working -D form and inspect the command-line parameter handling reached by JMeter. Done means the complete command runs successfully with multiple -J parameters and no errorlevel=255.

Written by the indexing model from the issue text.