[keccak-hash] Bump version

[dvdplm]

In the switch to depend on primitive-types a local dependency was used ({ path = "../primitive-types" }). And a new version was never published, which causes trouble for depending crates higher up the stack.

Bump to 0.2.0

Question: should the version be 0.2 here? I think so.

[ordian]

Not sure I understand what problem does this PR solve, could you elaborate?
(we need to publish keccak-hash 0.2, but that's a separate issue)

[dvdplm]

what problem does this PR solve,

Using path = "../path/to/dep" to specify dependencies is not allowed when publishing crates, so that's one problem. Another problem is that if you use [patch] to load some crates from a git branch and some others a your local checkout and those two patched crates share a dependency, then you'll end up loading two different crates, which, even if they're exactly the same code can cause hard-to-debug issues.
I think the only time it's ok to use a path in parity-common is when the dependency is below, i.e. for sub-crates.

[dvdplm]

I think the only time it's ok to use a path in parity-common is when the dependency is below, i.e. for sub-crates.

Hmm, and then I found this and now I'm confused again. How can that even work?

EDIT: aha, the code in the repo is not actually what was published

[ordian]

Do we want to close #146 or tackle it in a separate PR?

[dvdplm]

Do we want to close #146 or tackle it in a separate PR?

Separate PR. I think we have enough crate version churn to handle atm.

[ordian]

Hm, actually, let's wait for openethereum/parity-ethereum/pull/10670, seems like ethereum-types would work better as a dependency.

[ordian]

Closing in favor of #158.