[Source-Postgres] Rollback to 2.1.1 in case 3.0.0 fails [DO NOT MERGE]

[nguyenaiden]

What

In the case that we need to rollback this change. This PR redirects version 3.0.0 to point at 2.1.1. In the case that we need to rollback, this PR will be merged, and another PR will be submitted with version 3.0.1 that removes the previous changes. Also, postgres.md changelog will be updated with version 3.0.1 stating the rollback.

[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.

[github-actions]

Coverage report for source-postgres

There is no coverage information present for the Files changed

Total Project Coverage	69.92%	🍏

[nguyenaiden]

Closing as change is shipped and is stable