Use concrete signature types

[DaughterOfMars]

Description of change

This PR updates crypto and stronghold, and replaces byte arrays with the concrete crypto types.

Links to any relevant issues

• Closes Ed25519Signature could use stronghold/crypto types #511

Type of change

Choose a type of change, and delete any options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[semenov-vladyslav]

It looks like a simple fn from_u32_hardened could have solved the issue with repeated pattern .into_iter().map(Segment::harden).collect().

But the right solution seems to be to introduce a Bip44 type as all the bip32_chains in the code are in fact bip44_chains. BIP-44 has strict rules for hardening. We can apply the correct hardening rules (depending on the key type) when converting it into iterator.

[semenov-vladyslav]

bip44 PR. You can use slip10::Bip44 as the type of your chains. You can use [..].into() or Bip44::from([..]) to create Bip44 chains without the need to explicitly harden segments. You can use let sk: ed25519::SecretKey = bip44_chain.derive(&master_key).secret_key() to derive signing key, segments will be hardened automatically.

[kwek20]

I dont like this

.into_iter()
.map(Segment::harden)
.collect(),

Maybe we can add a helper method to Segment or something?

edit: ah i see vlad thought the same-ish :D