Improve key naming clarity and consistency across REST requests #683

[demoncoder-crypto]

… Standardize on camelCase for REST API parameter names - Update README.md to document parameter naming conventions - Create new inline_pdf_example.sh with consistent naming - Fix inconsistent naming in several example files - Fixes #683

Description of the change

Motivation

Type of change

Choose one: (Bug fix | Feature request | Documentation | Other)

Checklist

• [x] I have performed a self-review of my code.
• [x] I have added detailed comments to my code where applicable.
• [x] I have verified that my change does not break existing code.
• [x] My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
• [x] I am familiar with the Google Style Guide for the language I have coded in.
• [x] I have read through the Contributing Guide and signed the Contributor License Agreement.

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[demoncoder-crypto]

I have made the asked changes let me know if its upto mark

[ossa-ma]

Looks good to me but I believe these examples need to be verified and tested by someone internal to Google before they can proceed with merging the PR and closing the issue.

[demoncoder-crypto]

Thanks. If anything else is needed or any changes. I am always up for it