Adapt optimiser-state tests to Optimisers 0.4.10
`adjust!` now reaches the rules inside an `OptimiserChain` set up for
Reactant (FluxML/Optimisers.jl#240), so test it plainly. Use `ClipGrad`
in the chain: Optimisers 0.4.10 throws a `MethodError` from `adjust!` on
a Reactant `ClipNorm`, which holds no device scalar. Also test `RAdam`,
whose step counter is an `Int` on the host and a tracked `Float32` on
the device, and note that a host state moved to the device freezes it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>