Fix incorrect array encoding in config produced by RollbarJsHelper

[vilius-g]

When building JS code with RollbarJsHelper and passing configuration
parameters that are arrays, those arrays in the final JS output are
incorrectly encoded as objects.

[bishopb]

Thanks for taking the time to submit this! I agree; the current code seems buggy.

Digging a little, looks like JSON_FORCE_OBJECT was introduced back in 2017 by @rokob. I think the intent of that change was to ensure the configuration object at the highest level was always an object, but it seems to have neglected the side effect of forcing deep PHP arrays to JSON objects (eg, a configuration of [ "a" => [ ] ] produces {"a":{}} instead of the desired {"a":[]}.

We'll get this in the pipeline for change soon.

[rokob]

Yeah I was trying to only force the top-level to be an object. PHP never ceases to amaze me. I see now in the docs that there is a user comment about this behavior. Although the main docs don't mention anything about this being applied to the entire structure:

JSON_FORCE_OBJECT (int)
Outputs an object rather than an array when a non-associative array is used. Especially useful when the recipient of the output is expecting an object and the array is empty. Available as of PHP 5.3.0.

[danielmorell]

@vilius-g sorry about the long delay! This looks great! I think we just need to fix the merge conflicts before getting this in. Can you do that?

[vilius-g]

I have fixed merge conflicts.

There seems some issue with CI, but it is possibly one-off as I am unable to reproduce it.

[danielmorell]

Thank you @vilius-g. I ran the failed tests again and they passed. We sometimes get false negatives when performing the network part of the test suite.

This looks great! Thank you for the work on this!