fix: adds client side filtering to export

[a-rampalli]

What

We wanted to fix the param being sent to export api so that we get data from the timestamp we want. Turns out if we do that ordering of records will not hold in the api response we get. Not having ordering will create problems in us storing state at regular intervals. This is a bigger problem because of the unexpected end of json errors
So we are doing client side filtering of records fetched from export api.

Testing

The records now are ordered by time and also have time value more than state {"export": {"time": "2023-08-09T10:59:59Z"}}

If we set state value greater than end date we get 0 records as intended

[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 and you've followed all steps in the Breaking Changes Checklist
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• 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
• The connector tests are passing in CI
• You've updated the connector's metadata.yaml file (new!)
• 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.