refactor(core): make crypto module into crate

[SuperFluffy]

Summary

Breaks out astria_core::crypto to crate astria-core-crypto.

Background

One needs to import the entire kitchensink that is astria-core even if one only wants to use a fraction of its types. That leads to extremely long compilation times because all of its dependencies need to be compiled.

This patch is the start to breaking out parts of astria-core into their own free standing crates, which astria-core then reexports.

A useful sideeffect of this change is that the coupling between the different parts of astria-core is reduced (for example, by removing the rarely used utility method SigningKey::try_address, allowing to decouple address and crypto logic).

Changes

• Move the module astria_core::crypto into new create astria-core-crypto and reexport under the astria_core::crypto alias (not breaking to consumers)
• Remove the tight coupling between the crypto and address parts of the stack by removing the SigningKey::try_address (rarely used and only inside a few tests) method and moving ADDRESS_LENGTH to a thin astria-core-consts crate (this is a breaking change for users of SigningKey::try_address).

Testing

Tests for astria core's crypto refinement types were moved to astria-core-crypto and left unchanged. Sequencer tests were updated to use Address::builder instead of SigningKey::try_address and otherwise also left unchanged.

Changelogs

Changelogs updated.

Breaking Changelist

• These changes leave all services untouched.
• These changes would be breaking the public API of astria-core due to the removal fo SigningKey::try_address but we don't provide any stability guarantees for it.

Related Issues

Part of #1798