Heroku Connect Reuse Existing Schema

### Required Terms

- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)

### What service(s) is this request for?

Postgres, Connect

### Tell us about what you're trying to solve. What challenges are you facing?

Currently, Heroku Connect requires the dropping or renaming of an existing Postgres schema in order to recreate the Connect instance. This can be a problem if you have views in other schemas that reference tables in the Heroku Connect schema. It would be great if there could be more of an "in-place" approach to recreating Connect instances, where the schema and tables can be reused. Alternatively, it would be helpful if Connect instances did not need to be recreated for cases of a Salesforce sandbox refresh or change to the API version.