[maps] allow feature editing with vector tile scaling

[nreese]

Fixes #122049

This PR allows for feature editing when using vector tile scaling. Why? well, asking users to set various layer configurations to enable feature editing is a pain and puts up a barrier to usage. Why would we expect users to change scaling, edit features, and then change scaling back?

The user experience of editing features with vector tile scaling is a little off. Editing features causes the tile URL to change. This results in the entire source being removed from the map and then a new source appearing. This is a little jarring as drawing a feature results in all features being removed for a split second and then all features plus the new feature coming back. I still think its better than making users change scaling to edit features. Thoughts?

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[nreese]

@elasticmachine merge upstream

[nreese]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 1d8812c
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
maps	2.5MB	2.5MB	+103.0B

History

• 💚 Build #20449 succeeded 270c5ef
• 💚 Build #18551 succeeded 6da1233
• 💔 Build #18547 failed 68b1ad5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[nickpeihl]

The user experience of editing features with vector tile scaling is a little off. Editing features causes the tile URL to change. This results in the entire source being removed from the map and then a new source appearing. This is a little jarring as drawing a feature results in all features being removed for a split second and then all features plus the new feature coming back. I still think its better than making users change scaling to edit features. Thoughts?

I think the benefits of this feature outweigh the UI refresh. We should remove the friction for users as much as possible.

lgtm!

code review and tested in chrome.