Move secp256k1_recover to its own crate

[kevinheavey]

Problem

libsecp256k1 is a heavy dependency and the use case is niche

Summary of Changes

Moves secp256k1_recover out of solana-program and into its own crate

[kevinheavey]

The circular dependency check is failing but the premise of the check is wrong. It's complaining about the recommended way to activate a feature in tests: https://stackoverflow.com/questions/68618789/is-it-possible-to-enable-a-rust-feature-only-in-test

Update: turns out I don't need that to make the tests pass so we can worry about it another time

[kevinheavey]

Coverage failure means nothing to me: /solana/scripts/../ci/intercept.sh: command failed; please see /dev/null in artifacts

[0x0ece]

Is this intended?

[kevinheavey]

Yes, I defined it manually in the secp256k1-recover crate to avoid depending on solana-program in that crate:

#[cfg(target_os = "solana")]
extern "C" {
    pub fn sol_secp256k1_recover(
        hash: *const u8,
        recovery_id: u64,
        signature: *const u8,
        result: *mut u8,
    ) -> u64;
}