Remove Scrutinizer coverage upload steps from CI workflow

[aik099]

Summary

• Scrutinizer's build was permanently failing at its "Waiting for External Code Coverage" step (analysis errors out, timer stops, red status) regardless of PR content — root cause traced to the external_code_coverage tool being enabled in the Scrutinizer dashboard config.
• Coverage requirement is being disabled on the Scrutinizer dashboard side, so the ocular.phar upload steps in this workflow are no longer needed.
• CodeCov already covers coverage reporting in the same workflow (Upload Coverage to CodeCov step).

Test plan

• No functional test changes; verified the diff only removes the two Scrutinizer upload steps and workflow YAML is still well-formed.
• Confirm the "Scrutinizer" GitHub status check turns green after this merges and the dashboard coverage setting is off.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.72%. Comparing base (89a75a4) to head (3ff50cf).

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #119   +/-   ##
=========================================
  Coverage     97.72%   97.72%           
  Complexity      513      513           
=========================================
  Files            30       30           
  Lines          1493     1493           
=========================================
  Hits           1459     1459           
  Misses           34       34           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.