change order of key mapping transform

[misko]

Currently we perform key_mapping renames and then perform data_object transforms. However data object transforms have hard coded string values. This means that if we change the task and change the key_mapping the same hard coded data transforms will no longer work, i.e. key omat24_energy might not be present.
On the flip side, if we perform data transforms before key name remapping, this cleans up the transforms since most datasets have the keys energy and not datasetname_energy.

This PR changes the order so that we first perform data transforms, and then perform key renaming.

[codecov]

Codecov Report

Attention: Patch coverage is 37.50000% with 5 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/fairchem/core/datasets/oc22_lmdb_dataset.py	0.00%	4 Missing ⚠️
src/fairchem/core/datasets/ase_datasets.py	50.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/fairchem/core/datasets/lmdb_dataset.py	80.00% <100.00%> (+0.20%)	⬆️
src/fairchem/core/datasets/ase_datasets.py	87.09% <50.00%> (ø)
src/fairchem/core/datasets/oc22_lmdb_dataset.py	15.20% <0.00%> (-0.13%)	⬇️

[rayg1234]

Thanks for cleaning this up!