Report called arguments based on FPD config
    
    FPD wrapper call reports from pages now contain arguments only if specified by FPD wrapper evaulation configuration.
    This had a large impact on the performance of wrapped calls with large arguments (e.g. image or audio data arrays
    passed to functions like readPixels) where it was neccessary to serialize, postMessage, and deserialize them.
    FPD currently doesn't track any call arguments that are likely to get large; the current count of wrappers requiring argument tracking is just 12 (+2 exceptions in fp_code_builders.js that this change doesn't apply to).