chore(mapbox) use maplibre v3 instead of mapbox v1

[chrisgervang]

For #8549

Note: maplibre v4 fails in our example due to a CORS issue, likely introduced with maplibre/maplibre-gl-js#3233. Needs more investigation.

Change List

• use maplibre v3 instead of mapbox v1 in pure js example

[Pessimistress]

There is a strong pushback from the maplibre community against using the "mapbox" brand name with their library for branding and legal reasons. For example, they would like us to publish a new submodule @deck.gl/maplibre with MaplibreOverlay (maybe not at this time), and have get-started boiler-plate examples named "maplibre" (we probably should).

I know this example is named after the submodule, but better not mix the two unless we have to.

[chrisgervang]

I think that's a good direction too given they'll only diverge overtime. Maybe the new module could be added to 9.1 roadmap? In the meantime, I can rename folders and library references to maplibre.

[coveralls]

Changes unknown
when pulling 0a80577 on chr/pure-js-mapbox-to-maplibre-v9
into ** on master**.

[Pessimistress]

In the meantime, I can rename folders and library references to maplibre.

To be clear I did not advocate for "rename". We should not use the names "Mapbox" and "Maplibre" interchangeably. It's now equally confusing for the users of both libraries. We need separate doc pages and examples for both.

[HarelM]

@chrisgervang which version 4 of maplibre did you use?
Is it possible that this issue was fixed in the latest version?
See the following issue:
maplibre/maplibre-gl-js#3680
In any case, if you are experiencing issues with maplibre v4 I would like to know as this version is new and there were a lot of refactoring there. I would be surprised if we introduced CORS issues, but anything is possible :-)

[chrisgervang]

Thanks @HarelM, I saw that issue too but it doesn't seem related. I've opened #8551 to figure this out