Use range dependencies

[tcharding]

The last couple of releases of bitcoincore-rpc and bitcoin_hashes have not required code changes here. This means we can use range dependencies. The benefit is that it makes the upgrade of other crates that use bitcoind easier.

Tested by pinning hashes with:

• cargo update -p bitcoin_hashes@0.13.0 --precise 0.13.0
• cargo update -p bitcoin_hashes@0.14.0 --precise 0.14.0

And then pinning bitcoincore-rpc with all of the dependencies in the range and running cargo check --all --all-features --all-targets

E.g (using cc as alias to the cargo check command above)

• cargo update -p bitcoincore-rpc --precise 0.17.0 && cc
• cargo update -p bitcoincore-rpc --precise 0.18.0 && cc
• cargo update -p bitcoincore-rpc --precise 0.19.0 && cc

Bump the crate patch version so we can release this change in a point release. Since this is a pre-1.0 crate I believe this is ok to do.

[tcharding]

Hey @RCasatta, the changelog entry for the 0.35.x series is missing. Do you want me to add that? (either as part of this or in a separate PR?)

[RCasatta]

utACK 2ff068fc0ed833fb4890782912e9192ce50b1de3

the changelog entry for the 0.35.x series is missing. Do you want me to add that?

Yes please, and sorry that I forgot.

either as part of this or in a separate PR?

As you prefer

[tcharding]

Done! I put a separate patch up the front for the missing changelog entries, this PR as a patch, and then a final "bump version number" patch for you to tag and release please.

Also the tag for v0.34.2 is missing. Looks like it should have been on commit c5b2184 Bump minor version.

[apoelstra]

utACK 76947495a36c8e836a693c26a9a434501f85d217

[tcharding]

Can we get this in please @RCasatta?

[RCasatta]

utACK 76947495a36c8e836a693c26a9a434501f85d217

Sorry for taking so long, I forgot

going to release 0.35.2 soon

[tcharding]

No sweat, thanks man!