refactor!: migrate from snafu/n0-snafu to n0-error

[Frando]

Description

Migrates the repo from snafu/n0-snafu to n0-error.

Note: This PR is mostly AI generated after a detailed instruction set on how to do the migration.
I gave the diff a line-by-line review and fixed things up where the AI made mistakes.
Afterwards, I gave the diff another review while adding a few more from_sources and removing manual error mappings.

Breaking Changes

• All error structs and enum variants now have a meta: n0_error::Meta field
• All backtrace fields are removed on error enums and structs

Notes & open questions

Change checklist

• Self-review.
• Documentation updates following the style guide, if relevant.
• Tests if relevant.
• All breaking changes documented.

[github-actions]

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/net-tools/pr/59/docs/net_tools/

Last updated: 2025-11-03T15:29:29Z

[matheus23]

Note: Before next release the iroh-metrics dep of portmapper should be bumped to iroh-metrics 0.37 after n0-computer/iroh-metrics#56 is merged & released

I have a hard parsing this sentence. Does this mean this PR is blocked on a release of iroh-metrics?

[Frando]

Note: Before next release the iroh-metrics dep of portmapper should be bumped to iroh-metrics 0.37 after n0-computer/iroh-metrics#56 is merged & released

I have a hard parsing this sentence. Does this mean this PR is blocked on a release of iroh-metrics?

No, the PR is not blocked. But we should do a separate PR that bump iroh-metrics to 0.37 and n0-watcher to 0.4.1 before doing the (breaking) releases of portmapper and netwatch. Reworded the sentence in the PR description.