fix(js-client): Update method params type to be optional when all param keys are optional

[CalebBarnes]

Summary

This PR improves the developer experience by addressing issues with parameter typing in the API client:

• Methods with no parameters (e.g., getCurrentUser) incorrectly required passing something like getCurrentUser(undefined).
• Methods where all parameters are optional (e.g., listSites) required passing an empty object, even though no parameters were necessary.

These issues are resolved by conditionally setting the params type to either void or void | Params<{...}>, depending on the method's parameter requirements.

Changes

• Added AreAllOptional type to check if all keys in a type are optional.
• Added IsPathAndQueryOptional type to check if all parameters for a method are optional.
• Renamed CombinedCaseParams to Params for better readability in IDEs.
• Updated params type:
  • void for methods with no parameters.
  • void | Params<{...optional params}> for methods where all parameters are optional.
• Refactored OperationParams to simplify logic and moved repetitive checks into ExtractPathAndQueryParameters.

Example screenshots

Method with no parameters (getCurrentUser):

Method with all optional parameters (listSites):

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures
  we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
  something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures
  your code follows our style guide and passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

[serhalp]

LGTM