fix: json mode and human mode disagree on exit codes and aggregates

[andriypolanski]

Summary

1. gitt issues list --id — Missing on-chain issue: JSON already exited non-zero with a structured error; human mode exited 0 after a soft warning. Both paths now use the same helper as other issue commands (handle_exception) so exit code and error shape stay consistent.

2. gitt miner check --json-output — The top-level invalid count mixed “no PAT” (has_pat is False) with “invalid PAT” rows. JSON now exposes no_pat, invalid_pat, and no_response (plus valid), matching the human table semantics. invalid is removed from the JSON payload (breaking change for scripts that read that field).

Related Issues

Closes #723

Type of Changes

• Bug Fix

Tests

• tests/cli/test_issues_list_json.py — test_issues_list_human_missing_issue_exits_non_zero
• tests/cli/test_miner_commands.py — TestPatCheckAggregateCounts (imports _pat_check_aggregate_counts from miner helpers)

Migration notes (miner check JSON)

• Replace reads of invalid with no_pat + invalid_pat, or derive from results.
• no_response still means rows classified as no response (including cases that do not match the other three categories).

Test plan

pytest tests/cli/test_issues_list_json.py -q
pytest tests/cli/test_miner_commands.py::TestPatCheckAggregateCounts -q

[andriypolanski]

@anderdc
I just resolved conflict with https://github.com/entrius/gittensor/pull/724/conflicts
Please review.

[andriypolanski]

@anderdc
Could you please let me know why task check is failed?
If leave comment, I will fix constantly.

[anderdc]

Fix CI

[andriypolanski]

@anderdc
Sorry, Could you please let me know what I have to do?
Thanks

[andriypolanski]

Hi, @anderdc
I just checked failed CI test and fixed.
Please review again.
Thanks