TileLayer should be able to handle rotations without trying to fetch tiles beyond the given extent

[jeffpeck10x]

See comments in this PR #5080 from 2020 where @ilan-gold implemented a great solution for handling arbitrary modelMatrix inputs for the TileLayer.

One minor hiccup in that solution is that when the extent is recalculated for the given modelMatrix, there is seemingly some imprecision that leads to occasional 404s when there is a request for a tile that is outside the given bounds (provided in the extent prop bbox).

In that discussion, I proposed a workaround to adjust the extent to account for the margin of error:

function padExtent(
  bbox: [number, number, number, number],
  padding = 0.1,
) {
  return [
    bbox[0] + padding,
    bbox[1] + padding,
    bbox[2] - padding,
    bbox[3] - padding,
  ];
}

But, I am opening this discussion to see if there is a more elegant general purpose solution for the TileLayer to handle this small issue.

---

I should note, I am not 100% sure that the result of the extent transformation is actually the problem here, but as a simple example, let's rotate two points 90 degrees:

const toptLeftPoint = [0, 0];
const bottomLeftPoint = [0, 1234567];
const modelMatrix = new Matrix4().rotateZ(Math.PI / 2);  // Rotate 90 degrees on z-axis
console.log(modelMatrix.transformAsPoint(toptLeftPoint));
console.log(modelMatrix.transformAsPoint(bottomLeftPoint));

Result:

[0, 0]
[-1234567, 7.559542624414753e-11]

(of course, that rotated bottom left should really be [-1234567, 0])

The resulting transformed extent can potentially cause the TileLayer to try to fetch tiles that are beyond its bounds.