Consider updating maximumScreenSpaceError to 1.5 by default

[mramato]

Spun out of #3279

Now that our terrain and imagery system has been upgraded (#7061), would it make sense to lower the maximumScreenSpaceError default to something like 1.5? This would increase tile downloads slightly but would also increase visual quality and could better align with what people expect from 2D top-down views.

We should do a head-to-head comparison of various settings and see what the request/performance metrics look like. A slightly tweaked test I used in #7061 should work well for this too: #7061 (comment)

[mramato]

@kring suggests 1.33 as a possible optimal value in #3279 (comment)