Running bootstrap triggers a re-index of the entire schema

[jvanderen1]

I notice that when I re-run boostrap, the schema re-indexes entirely. This is not ideal for a few reasons:

• Nothing should have changed with boostrap being called multiple times. The appropriate triggers and replication slots should not be re-added.
• Anytime we wish to add/remove a table or create a new index, the bootstrap command will re-index every schema. A partial solution for us is to break the schema.json into multiple files, which would not be ideal.