Fix RNG key checking

[dakinggg]

What does this PR do?

Likely with pytorch 2.4, the keys in the state dict include lots of things, and they end up in the planner.

This means that the keys that include the string "rng" in a checkpoint can be like this

['state.integrations.huggingface.tokenizer.tokenizer.json.content.model.vocab.Ġrng',
 'state.integrations.huggingface.tokenizer.tokenizer.json.content.model.vocab._rng',
 'state.integrations.huggingface.tokenizer.tokenizer.json.content.model.vocab.rng',
 'state.integrations.huggingface.tokenizer.tokenizer.json.content.model.vocab.(rng',
 'rng.0.python',
 'rng.0.numpy',
 'rng.0.torch',
 'rng.0.cuda',
 'rng.1.python',
 'rng.1.numpy',
 'rng.1.torch',
 'rng.1.cuda',
 'rng.2.python',
 'rng.2.numpy',
 'rng.2.torch',
 'rng.2.cuda',
 'rng.3.python',
 'rng.3.numpy',
 'rng.3.torch',
 'rng.3.cuda',
 'rng.4.python',
 'rng.4.numpy',
 'rng.4.torch',
 'rng.4.cuda',
 'rng.5.python',
 'rng.5.numpy',
 'rng.5.torch',
 'rng.5.cuda',
 'rng.6.python',
 'rng.6.numpy',
 'rng.6.torch',
 'rng.6.cuda',
 'rng.7.python',
 'rng.7.numpy',
 'rng.7.torch',
 'rng.7.cuda']

The check in our code for processing rng keys is way too lenient, and tries to process the state integrations keys in this example. This PR makes the check stricter.

Manual test:
Run that fails on dev resuming: resumption-metadata-resume-1-EzxHw6
Run that success on this PR resuming: resumption-metadata-resume-fix-1-vhfchJ