[Refactor] Consider the varying Zoom level values for the Vector Tile API

[Rubix982]

Is your suggestion related to something in the interface of the package? As discussed in the discord chat, the vector tiles API in the APIv4 documentation may be included from having a constant zoom 14 level, to also including smaller images from zoom levels 15, 16, and 17.

Is your suggestion related to the documentation? This issue will act as a thread to keep in check the code changes that might happen in relation to the documentation updates regarding zoom levels.

Any other request/features, and their solutions you'd like NA

Describe alternatives you've considered NA

Additional context

• Our API/tiles may start supporting zoom 14, 15, 16, and 17 soon, not just 14. This means we can download at smaller scales, what we discussed about breaking the download into smaller pieces might be worth thinking about just within this range of tiles. We will review some scenarios for this if the change happens
• Mercantile still will do this, if we do not specify the zoom size it will choose one, it tries to go for the smallest. But we could make it say,
  1. Get bbox from the user
  2. Request starting at zoom 14
  3. If only 1 tile is returned, then go to zoom 15. If only 1 still returned, go to 16, and so on until 17
  4. If multiple tiles are returned, then we are at the most efficient method already, so request each tile then trim the resulting features to return only what is in the box
  5. Download and merge the data from all tiles. Having multiple tiles means downloading the most specific to the bbox without too much extra data.