Support relative path for "path-to-lcov" argument

[KeisukeYamashita]

What

When I ran the following step after my test, the step failed

- name: Coveralls
      uses: coverallsapp/[email protected]
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
        path-to-lcov: ./my/path/relative.info

with the the error Lcov: file not found while if I specify with absolute path, it successes.

- name: Coveralls
      uses: coverallsapp/[email protected]
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
        path-to-lcov: ${{ github.workspace }}/path/relative/lcov.info

[PaulRBerg]

I don't think that this bug still exists. In my workflow, I'm providing the path like this:

path-to-lcov: "./packages/amm/coverage/lcov.info"

And it works.