feat: implement backoff for snowpipe streaming authorization errors

[shekhar-rudder]

Description

This PR introduces a backoff mechanism when creating channels in the Snowpipe streaming destination. If an authorization error is encountered at the schema, table, or column level, the backoff ensures that we avoid repeatedly attempting to connect to Snowflake unnecessarily.

• Added a new struct authzBackoff in manager to store backoff related state
• Refactoring: Added managerCreator as a field in the manager for making the code testable.
• Until now, any error encountered while creating the channel for the discards table resulted in the job being marked as aborted. In this PR, the behavior has been updated to mark the job as failed, allowing it to be retried.
• Backoff is applied whenever an authorization error is encountered.
• Backoff is being cleared whenver channels for all the tables are being created without any authz error

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

Attention: Patch coverage is 89.02439% with 9 lines in your changes missing coverage. Please review.

Project coverage is 74.80%. Comparing base (8a186e5) to head (b5a1417).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
...tionmanager/snowpipestreaming/snowpipestreaming.go	86.36%	4 Missing and 2 partials ⚠️
...yncdestinationmanager/snowpipestreaming/channel.go	80.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5399      +/-   ##
==========================================
- Coverage   74.82%   74.80%   -0.03%     
==========================================
  Files         438      438              
  Lines       61331    61404      +73     
==========================================
+ Hits        45893    45935      +42     
- Misses      12895    12931      +36     
+ Partials     2543     2538       -5     

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

[RanjeetMishra]

1. Should we set MaxInterval as say 1 hr? This would mean once issue is resolved around snowflake permissions it will resume working by next 1 hour? Also from correctness perspective, overflow in backoff package is handled as maxInterval.
2. Are we using cenkalti/backoff/v4 elsewhere as well. I see in v5 pattern of initializing has been changed.

CC: @achettyiitr

[achettyiitr]

Are we using cenkalti/backoff/v4 elsewhere as well. I see in v5 pattern of initializing has been changed.

In rudder-server, we are still using v4. We haven't upgraded to v5 yet.

[shekhar-rudder]

1. Made MaxInterval as 1hr

[RanjeetMishra]

Would this mean we end up invoking .NextBackoff as many times as size of uploadInfos?

[shekhar-rudder]

Updated the code to set backoff only once