Upgrade protomaps and use it for region mapping

[tephenavies]

What this PR does

Upgrading protomaps to support compressed tiles, pmtiles archive version 3 and using protomaps renderer for region mapping.

• Remove MapboxVectorTileImageryProvider
• Update ProtomapsImageryProvider to accept a feature info function similar to

  terriajs/lib/Table/createRegionMappedImageryProvider.ts

  Lines 183 to 239 in 40d6f99

  	const getImageryLayerFeatureInfo = action(
  	(
  	style: TableStyle,
  	feature: VectorTileFeature,
  	currentTimeRows: number[] | undefined
  	) => {
  	if (isDefined(style.regionColumn?.regionType?.uniqueIdProp)) {
  	const regionType = style.regionColumn!.regionType!;
  	const regionRows =
  	style.regionColumn!.valuesAsRegions.regionIdToRowNumbersMap.get(
  	feature.properties[regionType.uniqueIdProp]
  	) ?? [];
  	const rowId = getImageryLayerFilteredRow(
  	style,
  	currentTimeRows,
  	regionRows
  	);
  	if (!isDefined(rowId)) return;
  	style.tableModel.tableColumns;
  	const rowObject = style.tableModel.tableColumns.reduce<{
  	[key: string]: string | number | null;
  	}>((obj, column) => {
  	obj[column.name] = column.valueFunctionForType(rowId);
  	return obj;
  	}, {});
  	// Preserve values from d and insert feature properties after entries from d
  	const featureData = Object.assign(
  	{},
  	rowObject,
  	feature.properties,
  	rowObject
  	);
  	const featureInfo = new ImageryLayerFeatureInfo();
  	if (isDefined(regionType.nameProp)) {
  	featureInfo.name = featureData[regionType.nameProp] as string;
  	}
  	featureData.id = feature.properties[regionType.uniqueIdProp];
  	featureInfo.properties = featureData;
  	const terriaFeatureData: TerriaFeatureData = {
  	rowIds: isJsonNumber(regionRows) ? [regionRows] : [...regionRows],
  	type: "terriaFeatureData"
  	};
  	featureInfo.data = terriaFeatureData;
  	featureInfo.configureDescriptionFromProperties(featureData);
  	featureInfo.configureNameFromProperties(featureData);
  	return featureInfo;
  	}

Test me

Checklist

• There are unit tests to verify my changes are correct or unit tests aren't applicable (if so, write quick reason why unit tests don't exist)
• I've updated relevant documentation in doc/.
• I've updated CHANGES.md with what I changed.
• I've provided instructions in the PR description on how to test this PR.

[AnaBelgun]

Update 15 March:

• testing before PR review and merge

[tephenavies]

Doesn't work with feature information properly yet. CSV values are missing from the table but vector tile attributes are making it through.

[AnaBelgun]

@steve9164 check this #7144 / talk to @nf-s

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ tephenavies
❌ nf-s
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[nf-s]

Bumped into #7144