No need to check for free consilio index ids
We need to stop doing this because
- it gives startup ordering issues (updateindices may run before consilio is started)
- only dbserver reuses older catalog.ids. you should be using postgresql
- only consllio uses indexids this way. a proper fix (eg guids instead of ids) would not help elasticsearch
- this is really only an issue if your consillio regularly outlives your database. mostly a stage-development issue... but why aren't those on postgresql yet?