V2 - Potential OAuth issues in some eBay Commerce and Sell OpenAPI contracts

This library generates most of its code directly from eBay’s published OpenAPI contracts.

While working with these specs, I found that some Commerce and Sell APIs appear to have incomplete or inconsistent OAuth2 definitions (for example, missing flows). The APIs that required patching are listed in MISSING_OAUTH_SCOPES in [generate_code.py](https://github.com/matecsaj/ebay_rest/blob/main/scripts/generate_code.py).

I have attempted to fill in the gaps where possible, but the required OAuth information is scattered across multiple areas of eBay’s documentation. In some cases, it is unclear which flow (authorizationCode vs clientCredentials) or which scopes are truly required, so it’s possible that a flow or scope is missing or incorrectly inferred.

I’ve added unit tests to validate the generated code, but I cannot fully exercise all APIs because my eBay developer account does not have sufficient privileges for some Commerce and Sell endpoints.

If you encounter permission or authentication issues with any Commerce or Sell API while using this library and are willing to collaborate, please open an issue or comment here. Confirmation from accounts with broader access would help verify and correct the OAuth configuration in the affected contracts.

Start with scripts/generate_code.py and the MISSING_OAUTH_SCOPES list, then compare the affected Commerce and Sell contracts with eBay’s OAuth documentation. Review the existing unit tests and validate the generated code where account access permits; done means the required flows and scopes are confirmed for the affected APIs.

Written by the indexing model from the issue text.