fix: include bootnodes in /status and /status/peers

[martinconic]

Checklist

• I have read the coding guide.
• My change requires a documentation update, and I have done it.
• I have added tests to cover my changes.
• I have filled out the description and linked the related issues.

Description

Fixes #5111. The peer counts reported by /peers, /status, and
/status/peers disagree on any node connected to a bootnode.

PR #4909 ("fix: exclude bootnode from protocol requests") made
kademlia's EachConnectedPeer / EachConnectedPeerRev always filter
bootnodes out via excludeFromIterator. That is the correct policy
for protocol traffic (pushsync, retrieval, puller, salud, kad's own
random-peer selection), but it also silently dropped bootnodes from
the two operator-facing status views, which iterate via the same
method. Meanwhile /peers reads p2p.Peers() directly and never
went through the kademlia filter — so it kept showing bootnodes.

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

AI Disclosure

• This PR contains code that has been generated by an LLM.
• I have reviewed the AI generated code thoroughly.
• I possess the technical expertise to responsibly review the code generated in this PR.