[Bug]: Normalization keys mismatch fails silently

[laserkelvin]

Expected behavior

When normalization parameters are passed, if there are no keys matched up we should throw an error or warning message to notify the user that nothing is being normalized.

Actual behavior

Currently, there is no "validation" persay of normalization keys passed, and so if they aren't matched with any of the targets, nothing happens.

Steps to reproduce the problem

Pass normalization kwargs, and have none of the keys match available targets.

Specifications

matsciml as of 46dd595