fix: prevent accidental removal of valid sector index announcements

[jacobheun]

Summary

We discovered an issue where when calling the Lotus Storage API we were not properly handling the multiple states that can be returned for a sector (Cache status, Unsealed/Sealed status). This could result in a sector being considered as removed.

This update adds a state to the database to account for the various Cache states a sector may be in. In most instances the Sealed/Unsealed status should ultimately be recorded, but in the instance that is not returned for some reason, we will record the cache status so that the sector is not removed. Only if no status is returned will we consider the sector as removed.

• Also fixes an issue where the database was not treating sector entries as unique, leading to numerous entries per sector instead of 1
• Ensures the Database starts up and runs any migrations before the rest of the index provider starts

TODO:

• Verify fix on SP
  • Ran multiple jobs to verify new index announcements were not being made, and we were no longer seeing incorrect removals (this previously was occurring on every run)
  • Deleted known entries from the DB and verified announcements were triggered

Note: This will result in a full index ingest for affected users.