Users are asked for apiVersion when no such field is expected in the adaptor

My small beef 🤏 🐄 with the current Generic OAuth2 implementation is that it asks users to provide an apiVersion whenever they create an OAuth2 credential.

As it turns out, many of our adaptors look for this apiVersion key in state.configuration and use it to... do stuff. But many don't. Why are we asking users to enter an apiVersion for every single type of OAuth2 credential if this data will never be used for anything? That feels quite misleading.

Thoughts on solutions:

• I don't think we can, in good conscience, explain to users that when they fill out the apiVersion field on their standard Google Sheets credential it will do… absolutely nothing!
• Maybe we change the GoogleSheets adaptor so it actually does something with that key? (I.e., maybe we change every adaptor that uses OAuth2 so that it respects this apiVersion key?
• When initially speccing the Generic Oauth2 implementation, I thought that when someone creates an OAuth2 client (aka "Credential Type") they would specify the mandatory_scopes, optional_scopes, and additional_fields. Since this OAuth2 client is essentially a "credential form generation" I felt it would be sensible to specify what extra fields you want to appear on that credential form. - https://github.com/OpenFn/lightning/issues/2034

Start with the Generic OAuth2 implementation and trace how credential forms handle apiVersion, additional_fields, mandatory_scopes, and optional_scopes. Compare that behavior with the GoogleSheets adaptor and the adaptors that read state.configuration.apiVersion; the issue needs a decided approach and defined completion criteria before implementation can begin.