Currently, attr_encrypted gem implements dirty attrs
without handling kwargs properly.

If we just replace using attr_changed? method with
calling attribute_changed?(attr), it fixes the warning

It allows us getting away without updating the gem