[Code scan] Align DPRc example type_map with its data metadata

[njzjz]

This issue was found by a Codex global scan of the repository at commit 19f9265.

The DPRc MACE and NequIP example inputs use this model type_map order:

deepmd-gnn/examples/dprc/mace/input.json

Lines 6 to 13 in 19f9265

	"type_map": [
	"C",
	"P",
	"O",
	"H",
	"OW",
	"HW"
	],

deepmd-gnn/examples/dprc/nequip/input.json

Lines 5 to 12 in 19f9265

	"type_map": [
	"C",
	"P",
	"O",
	"H",
	"OW",
	"HW"
	],

But the bundled data metadata uses a different order:

deepmd-gnn/examples/dprc/data/type_map.raw

Lines 1 to 6 in 19f9265

	C
	H
	HW
	O
	OW
	P

Input order: C, P, O, H, OW, HW
Data order: C, H, HW, O, OW, P

If DeePMD does not remap exactly as intended for this example, the same integer types in type.raw will be interpreted as different elements during training. Even if remapping is supported, the example currently looks inconsistent to users copying it as a template.

Suggested fix: align the example input type_map order with type_map.raw, or add a short comment/documentation note explaining the intended remapping behavior.