[CON-2958] feat: enable chargeOver read & write

[Jkarage]

Conventions

Read more: https://ampersand.slab.com/posts/deep-connectors-guide-6x4fhxne#ht0ds-reviewer-checklist

• Connector uses internal/components
• Metadata uses V2 metadata format
• Read supports pagination and incremental sync
• Raw response is returned as is for READ & METADATA, no formatting or flattening is performed.
• Write payloads should accept what ReadResults.Fields is returning. Any unnecessary nesting around the input is removed.
• Provider errors are mapped if non-standard (errors with 200 response code are converted to 4XX)
• Custom fields, if not human readable names, are resolved to readable names.
• Unit tests cover read/write/metadata logic (placed in /tests/)
• Appropriate object names are used. Objects need to be resources, not actions (jobs and not jobs.list).
• Modules are only being added because:
  • They share the same authentication scheme
  • The same base URL cannot be used to make a proxy call to objects in all modules
  • Different base URLs (drive.google.com vs google.com)
  • Object name collisions (same object name exists in two or more modules)

Read

For each read object:

• Insert screenshot of metadata fields from read object installation.

• Insert screenshot of Svix destination.

• Screenshot of operations on dashboard

Write

For each write object:

• Insert screenshot of dashboard.

• Insert screenshot of HTTP call.

Examples

Test data PR

[linear]

CON-2958 Enable support on connectors