[chore] Use query for GET/DELETE requests, per HTTP spec

[nwithan8]

Description

• Update client logic to use query parameters for GET/DELETE requests and body for POST/PUT/PATCH requests
• Consolidate .get, .post, .delete, etc. functions to single .do
• Denote URL and JSON key names for parameter serialization

No changes to end-user experience or user-facing function signatures

Testing

• Re-record all cassettes (due to parameter schema changes, fixture updates, expiration)

Pull Request Type

Please select the option(s) that are relevant to this PR.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement (fixing a typo, updating readme, renaming a variable name, etc.)

[Justintime50]

Only blocking until I can take a solid look at this. You weren't kidding, this is beefy. Probably necessitates a breaking-change release, thoughts? We can do that shortly as we have a few other items that can pair with it if we decide to go that route.

[jchen293]

lgtm, didn't find any typo or issue. Would be good to have another eyes on this PR

[jchen293]

Only blocking until I can take a solid look at this. You weren't kidding, this is beefy. Probably necessitates a breaking-change release, thoughts? We can do that shortly as we have a few other items that can pair with it if we decide to go that route.

I don't think it's a breaking change unless users have VCR cassettes with our Client Libs API interaction, then it could fail the tests. We already merged the Ruby PR for this change, so we have to make a call if we should hold off on the Ruby until the next breaking change.

[Justintime50]

praise: Nice work here!

I would like to see the function suggestion investigated, I think it'd be worthwhile to make a single unified interface since there are hundreds of callsites that could benefit from it.