codecov: improve coverage upload

[ivanvc]

Align running the code coverage upload with other workflows by executing it from a Makefile target.

Update the current GitHub workflow to call this new target.

I identified this improvement while migrating this workflow to a Prow job.

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.84%. Comparing base (9de211d) to head (6c86654).
Report is 4 commits behind head on main.

Additional details and impacted files

see 19 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #19364      +/-   ##
==========================================
- Coverage   68.98%   68.84%   -0.14%     
==========================================
  Files         420      420              
  Lines       35739    35739              
==========================================
- Hits        24656    24606      -50     
- Misses       9660     9708      +48     
- Partials     1423     1425       +2     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9de211d...6c86654. Read the comment docs.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, ivanvc, serathius

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahrtr,serathius]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ivanvc]

/cherry-pick release-3.6

[k8s-infra-cherrypick-robot]

@ivanvc: new pull request created: #19447

In response to this:

/cherry-pick release-3.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.