Make `==` , `hash` not depend on canonicalize?

https://github.com/JuliaDiff/ChainRulesCore.jl/pull/230
made == and hash use canonicalize.
https://github.com/JuliaDiff/FiniteDifferences.jl/pull/111 does the same to FiniteDifferences.to_vec
this is a problem if ever we are having fields that for example match to the properties rather than the fields.
This was brought up in https://github.com/JuliaDiff/ChainRules.jl/issues/285#issuecomment-708457503

One option might be to introduce a Maybe we should have a canonicalize(x, mode=propertynames) or just always use propertynames rather than fieldnames

But specifically for these cases:
For isequals instead we should probably check that any fields not in both are iszero.
For hash we might be able to drop any fields that are iszero or maybe just any that are Zero.

to_vec is harder and not for this repo.

Start by reading PR #230 and the linked ChainRules.jl issue comment to understand the canonicalize-based equality and hash change. Compare the proposed propertynames/fieldnames and iszero/Zero options, then determine consistent behavior for ChainRulesCore; no file or test is named, so the relevant equality and hash tests must first be identified.