mapbox component jest tests

[yen-tt]

added jest tests for Mapbox component, specifically for the two prop fields: getCoordinate and onDrag. The remaining props are best tested through storybook.

note that mapbox-gl is mocked as it seems to use some web browser functionality on initialization that is not supported in jest test environment (jsdom). Without mocking, jest would present an error Error: Failed to initialize WebGL..

• tried third party libraries jest-webgl-canvas-mock and jest-canvas-mock still result in more window properties access related errors ([TypeError: e.window.Worker is not a constructor], which could be resolve by manually mocking Worker, [TypeError: this.target.addEventListener is not a function]...).
• Looked into how pageJS test mapbox provider in their map component: the map wrapper component invoke a load function to construct a script tag from yext/components-tsx-maps and the assertions in the unit tests seem to check for the rendering of the wrapper component only and not waiting for the script to load. No content/interaction of the map was tested from my understanding.
• Looked into how mapbox-gl-js does their own testing: they had a couple util files to set up the environment for their tests (mock requests, mock HtmlCanvas/WebLG in window object, etc.).

I decided this complexity is probably unnecessary to add to the repo but we can discuss if other may think differently. We can have jest strictly test new isolated functionalities added from the component and leave all the UI rendering and mapbox interaction to storybook tests.

SLAP-2222
TEST=auto

new jest tests passed

[github-actions]

Current unit coverage is 89.12721893491124%
Current visual coverage is 73.77551020408163%
Current combined coverage is 89.64497041420118%