Source Mailchimp: Add expected records

[ChristoGrab]

What

Currently, we are reading from our internal Mailchimp account for CAT tests, so expected_records can't be populated in order to avoid sharing internal data. We do have an old sandbox account that has now been reactivated and can be safely used for testing purposes.

How

• Added expected_records for all streams other than Automations (need to upgrade to paid account to populate stream)
• Updated credentials in GSM
• Added missing enum value for type property in Campaigns stream
• In edge cases where a campaign has not yet received any clicks, the Reports stream returns an empty string for clicks.last_click property. This causes validation errors due to the declared date-time format. Added logic to exclude the property if it is an empty string.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 14, 2023 7:01pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[cgardens]

lgtm!

[lazebnyi]

LGTM
Minor comments left

[evantahler]

👍 Nice! I confirm that the expected records don't have PII (we made some fake test accounts)