Improve base selection to exclude bases based on backup version

[ashmrtn]

We've found rare but occasional need to force full backups for certain services when we update the persisted information. So far this logic has been added and maintained in the code base ad-hoc. However, it would be best to come up with a more robust solution that abstracts this situation to some degree. The abstraction is necessary because what backup versions are valid will vary between services

One way to handle this is to have individual services define a map of invalid base backup versions and pass this to the base selection logic. That will remove the service specific knowledge from base selection while still providing robustness across upgrades/downgrades of corso