Support automatically setting replication method based on stream metadata

[JohannesRudolph]

Some taps only support state for some streams, not for others. E.g. tap-pipedrive has this catalog

  "stream": "deals",
      "metadata": [
        {
          "breadcrumb": [],
          "metadata": {
            "table-key-properties": [
              "id"
            ],
            "forced-replication-method": "INCREMENTAL",
            "valid-replication-keys": [
              "update_time"
            ],
            "inclusion": "available"
          }
        },

For other streams, the forced-replication-method is set to "FULL". It would be great it target-bigquery could interpret those metadata instead of having to explicitly configure via loader config it my orchestration tooling (meltano).

[RuslanBergenov]

@JohannesRudolph, we have use cases when we want to set target replication method as APPEND, even though tap replication method is FULL_TABLE. We do this in order to preserve historical data.

Our current process is:

1. Pull replication method from target-bigquery config
2. If it’s not there, use append

Our new process will be:

1. Pull replication method from target-bigquery config
2. If it’s not there, pull it from JSON schema (new feature)
3. If it’s not there, use append

Our new feature should address your use case.