[Feature] When running `source-wand init`, it should look for existing dependencies

1. If it is already in the store (sourcecraft store, bld), setup the YAML pointer to the store (and dodge cloning)
- Tools: `bld`
2. If we have the package but we need a different version, we need the
- Upstream repository (to copy down the new version)
- Our local repository (where we are pushing the new version) >> make sure the names are the same

# What we are waiting for?
1. sourcecraft store (official launch)
2. Protocol for sourcecraft >> naming conventions, track, channel, etc.
3. The bld tool
4. Protocol for launchpad >> naming conventions, branches, etc.

Start with the `source-wand init` command and trace its dependency setup flow. The work is complete when existing `bld` or sourcecraft-store dependencies use YAML pointers without cloning, while different versions identify both upstream and local repositories with matching names. The issue notes that sourcecraft and launchpad protocols and the `bld` tool are still pending.

Written by the indexing model from the issue text.