[Feat] Tile3D Layer extent

Target Use Case

Highlighting an individual building using 3D tile layer in combination with masking via a geojson bounds is very useful and powerful, but, as I understand it, the entire 3d tile set is fetched.

This has a significant network load when using something like Google 3D tiles as a data source.

Proposal

Now that the deck's mask extension works great with 3D Tile Layer (Thanks @felixpalmer , it's awesome and very useful), I was wondering if it would be possible to add a extent restriction to the 3d tile layer, to reduce unnecessary network requests, in the same way that 2D tile layer has an extent prop.

It could be especially useful for when the viewstate has a lot of pitch but there is only one small part of the 3d tileset that is needed to be visible to the user.

Start with the Tile3D Layer and compare how the 2D tile layer handles its extent prop. Determine how an extent could restrict 3D tile fetching while preserving masking and pitched views. Done means the layer avoids unnecessary requests outside the requested extent and the behavior is validated for the stated use case.