Refactor/make peer info match geth

[obasekiosa]

Fixes #7808

Changes

• Restructures the admin_peers response

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Optional. Remove if not applicable.

Documentation

Requires documentation update

• Yes
• No

If yes, link the PR to the docs update or the issue with the details labeled docs. Remove if not applicable.

Requires explanation in Release Notes

• Yes
• No

If yes, fill in the details here. Remove if not applicable.

Remarks

Optional. Remove if not applicable.

[benaadams]

Need rebase

[Copilot]

Pull Request Overview

This PR refactors the admin_peers response to better match geth by restructuring the PeerInfo response and adding protocol-related details.

• Introduces a new optional Enr property with JSON serialization handling.
• Adds properties for Caps, Network (with a new NetworkInfo class), and Protocols in PeerInfo.
• Makes minor adjustments in AdminRpcModule to update node info.

Reviewed Changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/Nethermind/Nethermind.JsonRpc/Modules/Admin/PeerInfo.cs	Refactored PeerInfo with additional protocol and network details and minor comment improvements
src/Nethermind/Nethermind.JsonRpc/Modules/Admin/AdminRpcModule.cs	Removed a redundant blank line and added a comment about a repeated call in the constructor

Files not reviewed (2)

• src/bench_precompiles: Language not supported
• src/tests: Language not supported

Comments suppressed due to low confidence (1)

src/Nethermind/Nethermind.JsonRpc/Modules/Admin/PeerInfo.cs:69

• Using the null-forgiving operator on peer.OutSession may cause a runtime exception if both InSession and OutSession are null. Consider explicitly handling the case where both sessions might be null.

LastSignal = (peer.InSession ?? peer.OutSession!).LastPingUtc.ToString(CultureInfo.InvariantCulture);

[Copilot]

Typo found: 'availibale' should be corrected to 'available'.

Suggested change

	// keep extra info not availibale in get?
	// keep extra info not available in get?