Add test coverage check to CI.yaml

[thepetk]

What does this PR do?

Adds a new job for coverage inside the CI.yml file. More detailed we are updating the command:

code-coverage-report:
  runs-on: ubuntu-20.04
  steps:
    - name: Checkout
      uses: actions/checkout@v2.3.1
      with:
        persist-credentials: false
    - name: Set up Go 1.x
      uses: actions/setup-go@v2
      with:
        go-version: 1.19
    - name: Run tests
      run: go test -coverprofile cover.out -v ./...
    - name: Codecov
      uses: codecov/codecov-action@v2.1.0

This may runs twice the tests but it explicitly has an additional check and remains consistent with the devfile/library flow.

All preferences for codecov have been set with the addition of .codecov.yaml

Which issue(s) does this PR fix

fixes devfile/api#1164

PR acceptance criteria

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

• Unit/Functional tests

• Documentation

How to test changes / Special notes to the reviewer

I have created some tests runs here: https://github.com/thepetk/devfile-alizer/actions/runs/5543302687/jobs/10119130147?pr=2

[mike-hoang]

I noticed that in some of the other repos, we use the codecov gh action: https://github.com/devfile/library/blob/main/.github/workflows/codecov.yml#L20-L21

What do you think about:

1. Splitting the test into a separate workflow yaml (this does mean running the tests twice)
2. Using the code-cov-action which would add more details to the checks section

[thepetk]

I noticed that in some of the other repos, we use the codecov gh action: https://github.com/devfile/library/blob/main/.github/workflows/codecov.yml#L20-L21

What do you think about:

1. Splitting the test into a separate workflow yaml (this does mean running the tests twice)
2. Using the code-cov-action which would add more details to the checks section

Yes I thnk is a good catch. I like it and is more consistent as we are using the same way with the library :)

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@e55ee31). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage        ?   73.30%           
=======================================
  Files           ?        6           
  Lines           ?      618           
  Branches        ?        0           
=======================================
  Hits            ?      453           
  Misses          ?      136           
  Partials        ?       29           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[thepetk]

@mike-hoang updated the PR :)

[mike-hoang]

I like it! Small changes, but let's use the newest version of the codecov action to fix the annotation warnings

https://github.com/devfile/alizer/actions/runs/5543299324

[thepetk]

@mike-hoang I've bumped up both codecov and checkout :)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mike-hoang, thepetk

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

Needs approval from an approver in each of these files:

• OWNERS

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