This fixes a case where because we pass escapeQueryStrings: false to HTTPSnippet and don't escape query strings (instead relying on OAS style configurations), query strings in cURL snippets like [["$attributed_flow","=","FLOW_ID"]] wouldn't be escaped if the OAS doesn't use styles, resulting in a cURL snippet that couldn't actually be run.

$ curl --request GET \
>   --url 'https://mockbin.org/?where=[["$attributed_flow","=","FLOW_ID"]]' \
>   --header 'Accept: application/json'
curl: (3) [globbing] bad range specification in column 29

This fixes this problem by adding a new option to the cURL target called escapeBrackets that when present will manually escape [ and ]in the fullUrl data that it uses to chuck into the --url argument.

Resolves CX-347