🎉 Redshift Destination: Disable STATUPDATE flag when using S3 staging to speed up performance

[yahu98]

What

Describe what the change is solving

Apply optimization to redshift
#4871

How

Describe the solution

I changed the Redshift COPY command to speed up the process to copy csv files from staging s3 bucket to redshift. Specifically, I set the STATUPDATE parameter flag to be off. The STATUPDATE flag is responsible for running statistical computation to optimize future queries on the table. Since the table in our use case is temporary and the queries, computing these statisitics creates an unnecessary overhead. The performance saw an around 10% boost during my test runs.

## Recommended reading order 1. `RedshiftStreamCopier.java`

Pre-merge Checklist

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Secrets in the connector's spec are annotated with airbyte_secret
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• Code reviews completed
• Documentation updated
  • Connector's README.md
  • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
• PR name follows PR naming conventions
• Connector version bumped like described here

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• Credentials added to Github CI. Instructions.
• /test connector=connectors/<name> command is passing.
• New Connector version released on Dockerhub by running the /publish command described here

[sherifnada]

Thanks @yahu98 !