Describe the bug

Using the commands //pos1 and //pos2 while outside world bounds (<0, >255) will set the pos to that y value.

To Reproduce

1. a. Fly up to y=256 or go below y=0 and use //pos1 and //pos2
2. b. Alternative: Run //pos1 0,-10,0 and //pos2 0,260,0. Run //expand 1 u and observe the negative expand due to clamped region size.

Expected behavior

Expect the selection to get clamped to world bounds, such as what happens when using other selection commands like //expand, //shift. Alternative would be erroring instead.

Screenshots

Additional context

DataValidatorExtent ensures that gets/sets to the selection return air/noop. This does allow some interesting things like WG regions that are below bedrock etc. though. Unsure if that's problematic for anything. This is mostly just to be consistent with selection modification commands. Possibly a toggle/option of some sort could be added to allow out-of-bounds selections more generally?

I cannot replicate this. Likely not an issue.