Fix recovery issue for constraint indexes.

o This disables aggressive id reuse for schema store, meaning a restart is now required for reusing ids in this store.
o Addresses an issue where an index is dropped and then immediately reused and brough online, and the database then
  crashes. This creates a situation where recovery operations aimed at the original index will be targeted to the
  new index, after which the new index will be dropped and data unecessarily having to be recreated. In the constraint
  case it is fatal, because the constraint cannot come online before the index is populated, currently leading to a
  deadlock. This addresses all of the above issues.