Optimize layer iteration to prevent performance overhead.

[NonSwag]

Overview

Clamp the min and max y values to the min and max values of the chunk

Description

Adjusted the layer iteration logic in the Region class to use the minimum and maximum Y-values from the chunk. This prevents unnecessary iterations when getMinimumY or getMaximumY returns extreme values, improving performance efficiency.

### Submitter Checklist
- [x] Make sure you are opening from a topic branch (**/feature/fix/docs/ branch** (right side)) and not your main branch.
- [x] Ensure that the pull request title represents the desired changelog entry.
- [x] New public fields and methods are annotated with `@since TODO`.
- [x] I read and followed the [contribution guidelines](https://github.com/IntellectualSites/.github/blob/main/CONTRIBUTING.md).

[NonSwag]

I was not sure whether it would be more appropriate to use getMinSectionPosition or getMaxSectionPosition over getMinY or getMaxY
Input on that would be appreciated

[PierreSchwang]

Would be great if the variables would either be called minY instead of minLayer or keep them minLayer but put the bit shift directly after the Math.min/max instead of inside the loop - just so that the naming fits