feat: optional oauth support

[sanpj2292]

Description

Currently we would be attach OAuth framework specific things when we identify(auth.type) from the destination definition config to be OAuth, which would mean user would be restricted to go ahead with only OAuth not anything else.

In the past there have been use-cases where a destination would need to support multiple authentication mechanisms. We would need to provide multiple authentication mechanisms in the UI
In order to fulfil this, we have added auth.type as optionalAuth in the destination definition config. We are using this to identify if a destination optionally selected OAuth & also confirm if account id information is available in destination.config for attaching OAuth framework specific things

Linear Ticket

Resolves INT-2832

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.25%. Comparing base (6abcedd) to head (5079632).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5247      +/-   ##
==========================================
- Coverage   73.27%   73.25%   -0.03%     
==========================================
  Files         424      424              
  Lines       59960    59980      +20     
==========================================
+ Hits        43936    43938       +2     
- Misses      13559    13585      +26     
+ Partials     2465     2457       -8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.