[pselle]

Part of #65

Adds register_import! (behind a new testutils feature on stellar-registry), a test helper for contracts that use import_contract!.

import_contract! bakes the imported contract's on-chain address in at build time, so a unit test's Env has nothing at that address. register_import! resolves the name the same way and registers the contract there, so contract code needs no #[cfg(test)] switch around the import.

use stellar_registry::testutils::register_import;

register_import!(&env, our_dao);                           // the imported Wasm
register_import!(&env, our_dao, args = (&admin, 7u32));    // with constructor args
register_import!(&env, our_dao, contract = MockDao);       // a native mock instead

SAC names are a compile error for now; support follows in #82. The hello_caller fixture is excluded from the workspace because it can't compile without seeded cache files; just test-register-import seeds them and runs it in CI.

[chadoh]

I have been thinking about this for hours and I still haven't finished reading it all but it's time to give you my first wall of thoughts!!! 😂 😖 🙇🏼 🙇🏼 🙇🏼

(Take this as a good thing! You came up with an interesting solution to a problem I hadn't yet really thought through and it spurred some ideas!!)

Also, as always, I'm open to pushback on any of this! We don't have to do it the ways I'm contemplating, or we do not need to do them right now. Maybe it's fine to do an initial fast release with a cleanup update later.

[pselle]

Ok, I've resolved all the comments. I added typed args, but the from_network didn't make sense because STELLAR_NETWORK covers that.

I also added a recipe for testing through a contract build on testnet, alas that adds another fixture so that I can import that specific contract (alternatively, we could deploy hello_v1 or a different fixture to testnet ... but unverified/token is from the oz-wasms and I thought it fit well).

The perk of adding the fixture is that it shows the full example within the repo of how you'd use import_contract and then use register_contract, which I think was what you were aiming for. I like the token one too because it does have a handful of args, so it showcases the typed args well.

Resolved comments