Source SurveyMonkey: support oauth

[sherifnada]

Tell us about the problem you're trying to solve

With the release of Airbyte Cloud, we need to start supporting Oauth for this connector, since it's the recommended way of authenticating users into a SaaS application.

If this connector doesn't support oauth already (i.e: doesn't accept a client_id and client_secret) then we need to update its spec to accept those parameters. I suggest that this be a oneof nested inside a top-level field called "credentials":

{ credentials: { type: object oneOf: [ // api key, // oauth ] } }

See the connector spec reference in the docs for reference on how a oneof can be implemented.

This should be done in a backwards compatible manner i.e: users currently supplying authentication info in the config's top-level should not be impacted by this change.

Acceptance Criteria

1. The connector supports oauth webflow authentication with client_id/client_secret
2. Oauth properties are annotated properly. See this PR for an example

[sherifnada]

hey @VasylLazebnyk, there’s a follow up that we need to do to the survey monkey oauth PR according to this comment: #7433 (comment)

if the connector always accepts an access token, then there shouldn’t be two authentication mechanisms. The spec should look like the FB Marketing Spec, accepting only an access token, and assumes the connector is always doing oauth. Currently it doesn't make sense that we expose two auth mechanisms, because there is always only one: access key.

[avida]

Addressed in #7524 PR