Remove the redundant "← Back to X" link now duplicated by Breadcrumb on the detail pages

[Jagadeeshftw]

📌 Description

src/app/anchors/[id]/page.tsx and src/app/settlements/[id]/page.tsx both render a Breadcrumb (src/components/Breadcrumb.tsx) with a link back to the parent list, immediately above the AnchorDetail/SettlementDetail component. However, AnchorDetail (src/components/AnchorDetail.tsx) and SettlementDetail (src/components/SettlementDetail.tsx) each still render their own <Link href="/anchors">← Back to anchors</Link> / <Link href="/settlements">← Back to settlements</Link> at the top of their own markup — a leftover from before Breadcrumb was added. The result is two redundant "go back" affordances stacked on top of each other on every detail page.

🧩 Requirements and context

• Remove the standalone "← Back to X" Link from AnchorDetail.tsx and SettlementDetail.tsx, now that Breadcrumb (rendered by the parent page) already provides that navigation.
• Confirm neither component is used anywhere else without a Breadcrumb already present (e.g. check for other call sites before removing).
• No change to either component's data-loading, deactivate/execute/cancel, or ConfirmDialog behavior.

🛠️ Suggested execution

• Remove the leading <Link> block from src/components/AnchorDetail.tsx and src/components/SettlementDetail.tsx.
• Update src/components/AnchorDetail.test.tsx and src/components/SettlementDetail.test.tsx to drop any assertions on the removed link (and confirm the surrounding tests still pass).
• Spot-check src/app/anchors/[id]/loading.tsx and src/app/settlements/[id]/loading.tsx, which render their own back-link during the loading state and are unaffected by this change (they don't yet render a Breadcrumb).

✅ Acceptance criteria

• AnchorDetail and SettlementDetail no longer render their own "← Back to X" link.
• The Breadcrumb on both detail pages remains the sole back-navigation affordance.
• Existing tests are updated and continue to pass.

🔒 Security notes

No new attack surface; a UI de-duplication cleanup.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Ayinkx1]

Hi i would like to work on this issue please assign to me
I can do it perfectly

[github-actions]

Assigned @Ayinkx1 to this issue via repo automation. Please open a PR referencing this issue (e.g. Closes #238) when you're ready.

[grantfox-oss]

🦊 GrantFox — @Ayinkx1 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #238)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🦊 GrantFox — @Ayinkx1 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #238)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.