parseParameters requires a parameter to be JSON

TL;DR parseParameters shouldn't write a error level log for failure to JSON parse an arg. Make it debug level.

---

parseParameters works fine if you are sending your chaincode arguments as JSON objects or numbers. But litters error logs if you don't... which seems unnecessary.

Example:
['changeOwner', 'asset_1', 'user_2'] would result in 2 error logs
- "failed to parse param user_1"
- "failed to parse param user_2"

I guess the assumption is that developers will send those arguments as an array:
['changeOwner', ['asset_1', 'user_2']]
However, doing this makes destructing parsedParameters in ChaincodeBase.js:105 less useful
` let payload = await method.call(this, stub, this.getTransactionHelperFor(stub), ...parsedParameters);`

Example ideal use case:
```
// In chaincode
function changeOwner(asset, new_owner){
// Change the asset owner.
}
```

Start at parseParameters and its use in ChaincodeBase.js:105, then inspect how non-JSON arguments are logged. Confirm that ordinary string arguments no longer produce error-level messages while JSON parsing behavior remains unchanged; verify the resulting logging behavior with the project's existing checks.

Written by the indexing model from the issue text.