Bump concaveman to 1.2.0

[legrego]

Summary

Bumps concaveman to version 1.2.0. The previous version would not be compliant with a CSP which blocks unsafe-eval.

Notable change: mapbox/concaveman#17

This is a transitive dependency of @turf/center-of-mass. Ping @elastic/kibana-gis for review

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e77bc6d
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
maps	761	754	-7

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.6MB	2.6MB	-7.4KB

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

[thomasneirynck]

hi @legrego , so I'm not familiar enough with yarn to know the intricacies.

this PR updates the yarn-file directly. Will this change be "remembered". e.g. suppose we bump @turf/center-of-mass in the future, will it understand it needs to continue using at least concaveman 1.2.0? Right now, I guess any will do https://github.com/Turfjs/turf/blob/master/packages/turf-convex/package.json#L61

[legrego]

this PR updates the yarn-file directly. Will this change be "remembered". e.g. suppose we bump @turf/center-of-mass in the future, will it understand it needs to continue using at least concaveman 1.2.0? Right now, I guess any will do Turfjs/turf@master/packages/turf-convex/package.json#L61

@thomasneirynck yes, yarn will remember that we want version 1.2.0. The only reason it would change is if @turf/center-of-mass started requiring a specific version that wasn't compatible with 1.2.0 -- at this point, I don't expect that to happen anytime soon, so I think we're OK from that perspective.

My reason for asking y'all for review is to make sure your usage of @turf/center-of-mass continues to work the way you expect it to. I have no domain knowledge here to know if what I'm looking at is accurate or not 😄

[thomasneirynck]

centerofmass is used to calculate label positions. CI stays green, so automatically verified. I tested in chrome and labels remain correctly positioned for both vector tile and json based rendering.

[kibanamachine]

💚 Backport successful

✅ 7.x / #96055

This backport PR will be merged automatically after passing CI.