Reorder dedupe property types

[robertlong]

By deduping meshes after textures and materials you're more likely to be able to deduplicate more meshes.

[donmccurdy]

Thanks @robertlong! I think the unit tests for this feature predate the addition of material deduplication (in f69517b), and the unit test expects mesh deduplication to fail for two materials that differ only in name:

glTF-Transform/packages/functions/test/dedup.test.ts

Lines 82 to 100 in 0ffa610

	test('@gltf-transform/functions::dedup | meshes', async (t) => {
	const io = new NodeIO();
	const doc = await io.read(path.join(__dirname, 'in/many-cubes.gltf'));
	const root = doc.getRoot();
	t.equal(root.listMeshes().length, 501, 'begins with duplicate meshes');
	dedup({ propertyTypes: [PropertyType.ACCESSOR] })(doc);
	t.equal(root.listMeshes().length, 501, 'has no effect when disabled');
	// Put unique materials on two meshes to prevent merging.
	root.listMeshes()[0].listPrimitives()[0].setMaterial(doc.createMaterial('A'));
	root.listMeshes()[1].listPrimitives()[0].setMaterial(doc.createMaterial('B'));
	dedup()(doc);
	t.equal(root.listMeshes().length, 3, 'prunes duplicate meshes');
	t.end();
	});

Do mind updating the test to ensure that (1) meshes sharing materials that differ only in name WILL be deduplicated, and (2) meshes sharing materials that are meaningfully different WILL NOT be deduplicated?

[robertlong]

Sounds good, I'm also noticing that there's a bug de-duping materials+meshes in Third Room right now so I'm looking into that first

[donmccurdy]

@robertlong Would it be ok for me to merge this? Or do you think the bug in Third Room is related to this change?

[robertlong]

The bug was unrelated. This should be safe to merge 👍

[donmccurdy]

Ok, thank you!