Namespace destination tables

[ChristopheDuong]

What

Describe what the change is solving
Following-up on #1993, implements in destinations by using the new namespace fields

Implements #1921

How

Describe the solution

• Refactor the NamingTransformer to split into
  • a NamingHelper class: where we specify prefix/suffix to table/schema names
  • NamingTransformer classes: only handles identifier specificities to each destinations only
• Destination read and use namespace field in ConfiguredCatalog to specify where they should write the final table.

Pre-merge Checklist

• Run integration tests
• Publish Docker images

Recommended reading order

Refactoring naming utils classes to handle schema+table names:

1. airbyte-integrations/bases/base-java/src/main/java/io/airbyte/integrations/destination/NamingConventionTransformer.java
2. airbyte-integrations/bases/base-java/src/main/java/io/airbyte/integrations/destination/NamingHelper.java
3. airbyte-integrations/bases/base-java/src/main/java/io/airbyte/integrations/destination/StandardNameTransformer.java

Adapting destinations to new naming:

1. airbyte-integrations/connectors/destination-jdbc/src/main/java/io/airbyte/integrations/destination/jdbc/JdbcBufferedConsumerFactory.java
2. airbyte-integrations/connectors/destination-bigquery/src/main/java/io/airbyte/integrations/destination/bigquery/BigQueryDestination.java
3. airbyte-integrations/connectors/destination-csv/src/main/java/io/airbyte/integrations/destination/csv/CsvDestination.java
4. the rest

[michel-tricot]

I read this PR as a mechanical change. Is there one piece that you don't feel super comfortable with and where I should spend extratime?

[ChristopheDuong]

I read this PR as a mechanical change. Is there one piece that you don't feel super comfortable with and where I should spend extratime?

I would appreciate some pointers/answers from this comment: #1993 (comment) on how to handle the bumpversion...
I think making this backward compatibility is not so easy too if you have any ideas to share