Add --filter-by-connection-type flag to status command

[aliamerj]

Describe your changes

This PR introduces a new flag --filter-by-connection-type to the status command.
It allows users to filter peers by connection type (P2P or Relayed) in both JSON and detailed views.

Input validation is added in parseFilters() to ensure proper usage, and --detail is auto-enabled if no output format is specified (consistent with other filters).

Issue ticket number and link

Resolves #3883

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

[mlsmaycon]

@aliamerj I think we can limit this change to the status command only, similar to what we have for the other flags.

There is not much gain in filtering in the daemon/client

[mlsmaycon]

@aliamerj I think we can limit this change to the status command only, similar to what we have for the other flags.

There is not much gain in filtering in the daemon/client

It seems like I am becoming blind... please disregard my comment

[aliamerj]

@mlsmaycon
OK :)

[aliamerj]

@mlsmaycon

Is there anything should I update here ??

[mlsmaycon]

left a small comment @aliamerj

[mlsmaycon]

we should move this check into the skipDetailByFilters to align with current filter processing and output.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[aliamerj]

I just remembered why I initially didn’t include connectionTypeFilter in skipDetailByFilters.
To apply this filter, I first need to determine the connection type (connType), which depends on the Relayed flag inside the peer’s state. Since this logic didn’t exist in skipDetailByFilters yet, I needed to derive connType before calling the filter

we only want to skip a peer if its actual connection type doesn't match the filter. So instead of duplicating logic, I introduced a small getConnectionType() helper to keep things clean and consistent in both the filtering and output steps.

[mlsmaycon]

Thanks @aliamerj for the contribution