Throw exception on wrong config boundaries

While working on CASSANDRA-15234 we noticed usage of negative values where they are not supposed to be used. We fixed that for the parameters in scope - type duration, data storage and data rate but as brandon.williams pointed - there are other examples from the rest of the config that is good to be fixed too.

This ticket should handle:

• check the rest of the parameters, where negatives shouldn't be allowed they shouldn't be allowed

• ensure that whatever validations we apply to parameters during startup (check the DatabaseDescriptor) are applied also in the respective setters for those parameters.