Get rid off `Prior.test_valid_for_rescaling`?

This check has never failed for me. I know from doing performance tests in the past that this check costs us a couple of percent in runtime. It also appears a bit superfluous considering we don't regularly test if parameters lie within the defined range.