Guidance for Linking "Tools" when Publishing Policies

# Job Story
When publishing a policy that has Tool dependencies, I want clear guidance on how to proceed, so that I can publish my policy including Tool dependencies with clarity and don't have to begin searching through the methodology for Tool files and trace the entire dependency graph manually or searching IPFS for Tool links that are in the policy file by default but fail if the IPFS node hosting them is down.

# Acceptance Criteria
- [ ] publish Policies and have Tool dependencies resolved automatically
- [ ] or for each Tool dependency have a clear error message or instruction with how to publish my own tool versions

# Artifacts & Considerations
- Tools that don't resolve while searching IPFS — after a long time, this search eventually times out. There is no guidance on where to look or how to proceed next.
- dependency resolution is a common pattern and can be handled in other ways such as Apache Maven Repo or a service directory. With this pattern someone could point to a repo / service directory via an url e.g. guardian-tools-repo.hedera.com or tools-repo.verra.com and then leverage all linked and published tools from that location / provider.


Start with the policy publishing flow and the Tool dependency lookup described in the issue, then inspect how the methodology and policy file supply Tool links and how IPFS timeouts are surfaced. Done means either dependencies resolve automatically or each unresolved Tool produces clear instructions for publishing a usable version.

Written by the indexing model from the issue text.