[EPIC] Metrics tracking for connectors

[sherifnada]

Issues derived from google document: Measuring Connector Reliability

context

• Setup analytics project for tracking metrics #8638

Security

• Integrate airbyte repo with SonarQube #7881
• https://github.com/airbytehq/airbyte-internal-issues/issues/92

Data Integrity

• https://github.com/airbytehq/airbyte-internal-issues/issues/345
• https://github.com/airbytehq/airbyte-internal-issues/issues/346

Data Availability

• https://github.com/airbytehq/airbyte-internal-issues/issues/347
• https://github.com/airbytehq/airbyte-internal-issues/issues/348

Consistency of Sync & fault tolerance

• Track StandardSyncSummary with breakdown and more granular steps #4342
• Expose Partial Success Replication in the UI/API #3595
• https://github.com/airbytehq/airbyte-internal-issues/issues/349
• Diagnosis check: Determine remaining quota for a connector #8594
• Diagnosis check: Confirm oauth refresh_token & params validity #8595
• Validate Airbyte Json Message against the declared catalog #8596

Code stability / maturity

• [EPIC] Integrate Sentry #7956 / Implement proactive error tracking for connectors #2148

Load Speed

• [ ]

Ease of use

• [ ]

Popularity

• [ ]

[keu]

I think integration with Sentry should be here as well

[sherifnada]

@ChristopheDuong we should probably have an issue here for creating the analytics github project as well no?