While fixing RT-24566, the texture padding semantics bug, we noticed that the code that handles all of the cases of dealing with non-power-of-2 textures, zero/edge/repeat padding, and maximum and minimum texture sizes was inconsistent across the pipelines and inconsistent even within the code of one of those pipelines. We need to establish some consistent guidelines about how to deal with requests that are negative, 0, too large, or which go outside of those ranges after we adjust the dimensions due to platform restrictions.