fix: correct field name mismatch in performance test counters (#7860)

[Cypher-CP0]

Description
This PR fixes #7860

The performance test run counters on the site (Meshery page, Nighthawk page)
were always displaying 0 instead of the real run count.

Root cause: the API at https://cloud.layer5.io/api/performance/results/total
returns {"totalRuns": 160375}, but four components were reading
result.total_runs (snake_case) instead of result.totalRuns (camelCase).
Since that field doesn't exist on the response, the value was always
undefined, so the counter fell back to its initial state of 0.

Changes made:

• src/sections/Counters/index.js — fixed field name; added .catch() for
  error logging instead of failing silently.
• src/sections/Meshery/How-meshery-works/specs/data-card.js — fixed field
  name; this is the component actually rendered on
  /cloud-native-management/meshery, the page referenced in the issue.
• src/sections/Projects/Nighthawk/index.js — fixed field name; rendered on
  /projects/nighthawk, which has the same counter bug.
• src/sections/Meshery/Features-Col/index.js — fixed field name in the
  FeaturesTable component (also rendered on the Meshery page); also
  changed console.log to console.error in the existing .catch() for
  consistency with error-logging conventions used elsewhere in the codebase.

Local testing note: the API only allows CORS requests from the production
origin (layer5.io), so this can't be fully verified from localhost — it
will show a CORS error there regardless of the fix. Verified via the API's
actual response shape and will confirm final behavior on the PR preview
deployment.

Notes for Reviewers
None - straightforward field-name fix, no schema/API changes needed on our side.

Signed commits

• Yes, I signed my commits.

[github-actions]

🚀 Preview deployment: https://layer5.io/pr-preview/pr-7867/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

[KatalKavya96]

@Cypher-CP0 The changes look good. Could you please add a short screen recording from the PR preview showing the performance test counter displaying the correct value on the affected page?

stale

[rishiraj38]

There are too many lint-only changes, which makes it hard to review the actual code changes. Please revert the lint changes.