fix(doc): Fix broken links to zebra_network and zebra_state Config structs on doc.zebra.zfnd.org

[teor2345]

Motivation

What are the most important goals of the ticket or PR?

This PR fixes broken links to the zebra_network and zebra_state Config structs in https://doc.zebra.zfnd.org/zebrad/config/struct.ZebradConfig.html

Close #7048

PR Author Checklist

Check before marking the PR as ready for review:

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info?
  • Does the PR have a priority label?
• Have you added or updated tests?
• Is the documentation up to date?

This PR doesn't change Rust code behaviour, just the generated doc links.

Solution

• Use full paths to config imports to avoid a doc link bug

Related:

• Exclude zebra-test from the external docs build

Testing

I manually tested this locally with the doc build command we use in CI, and checked the files for zebra_network/zebra_network and zebra_state/zebra_state.

Review

This is a routine fix.

The generated docs from this PR should be checked for broken links in https://doc.zebra.zfnd.org/zebrad/config/struct.ZebradConfig.html

The "Deploy external docs to firebase" step logs a preview URL with the docs from each PR.

Reviewer Checklist

Check before approving the PR:

• Does the PR scope match the ticket?
• How do you know it works? Do the tests cover the PR motivation?
• Are there any blockers to merging this PR?
  • Can some changes go in new tickets or PRs?
• Manually test the PR

And check the PR Author checklist is complete.

Follow Up Work

If this happens again we should just link to docs.rs, it doesn't have this bug:

• devops: Stop publishing doc.zebra.zfnd.org and change links to docs.rs/zebrad/latest #7837

[arya2]

Looks good!