RingCentral

### App
RingCentral

### Summary:
Bind a RingCentral Production app override to Connect so end users do not choose Instance Type

### Details:
Project proj_6xszO7y uses RingCentral app ringcentral / app_mqeh2Q. App override ao_2EbUo6 sets cfmap.instancetype=https://platform and retains Pipedream managed OAuth. In @pipedream/sdk 3.1.3, what supported parameter binds this override to browser connectAccount or Connect Link? app=ao_2EbUo6 and the override name return App not found, oauthAppId=ao_2EbUo6 returns App not allowed, and app_override_id / appOverrideId are ignored. Please enable or document the supported selector so the contractor sees the branded initial Continue and then goes directly to RingCentral OAuth without the Instance Type screen. We need the normal success/error redirect and connection webhook behavior preserved.

### Screenshots:
No screenshots included

Start by tracing how browser connectAccount and Connect Link handle app selectors in @pipedream/sdk 3.1.3, then inspect validation for app overrides and oauthAppId. Test the RingCentral override ao_2EbUo6 and confirm that the supported selector skips Instance Type while preserving the normal OAuth redirects and connection webhook behavior.

Written by the indexing model from the issue text.