Run integrity check w. ignored pillar

Option to run integrity check, while ignoring a specific pillar

This means that if a given pillar isn't working, we can simply ignore it and perform integrity check with the pillars that are working, without having to create new settings files that exclude the "broken" pillar.

Important things to consider:

• What's the upper bound on pillars allowed to be ignored? Can't ignore all pillars, so max 1 if there exists more than 1 in the collection, ensuring t > 3 for agreement, also can't ignore all pillars that have data so we only use checksum pillars
• How should this be integrate this into the GUI dashboard, maybe list a list of checksum pillars that can be chosen to be ignored [None, pillar1, checksum2, ...] as a dropdown next to "Run complete integrity check" button
• Could be an option to remove it in the RepositorySettings, also need to obviously show which pillars are ignored on the dashboard
• Is there any side-effects that this can have, is there any edge case that we need to consider due to this new feature?

Talk to "FDB" about expectations for this kind of implementation.

It might also be worth it to have an option where if t>1/3 of pillars successfully received a file, we allow the BitRepository to return "SUCCESS", while still attempting to upload to the remaining pillars. This will speed up any service that relies on a reply from the BitRepository, while still assuring that the files will be stored at enough pillars to be able to potentially "repair" them on pillars where the upload failed, while trusting that the stored file is correct, as we have a majority vote that agree on the bytes received.