needs.<job id>.result is using steps conclusion instead of outcome

Thank you 🙇‍♀ for wanting to create an issue in this repository. Before you do, please ensure you are filing the issue in the right place. Issues should only be opened on if the issue relates to code in this repository.

• If you have found a security issue please submit it here
• If you have questions about writing workflows or action files, then please visit the GitHub Community Forum's Actions Board
• If you are having an issue or question about GitHub Actions then please contact customer support

If your issue is relevant to this repository, please include the information below:

Describe the bug
I've been trying to use needs context However if ever your job has continue on error flag set to true and you check the job result via the needs context you'll get success while the job actually fails

To Reproduce
Steps to reproduce the behavior:

1. Create a failing jobs with continue-on-error set to true
2. Create another job needing the first one and try to access the first job result

Expected behavior
Expected needs.job1.result to be failure even if flag continue-on-error is set to true

name: Test download Input
on:
  push:
      branches:    
      - master
jobs:
  job1:
    runs-on: ubuntu-latest
    continue-on-error: true
    steps:
      - name: "Check if artifact has already been built"
        id: dwnld
        uses: actions/download-artifact@v2
        with:
          name: ${{ steps.get-commit.outputs.commit }}_${{ matrix.apps }}
      - name: The job has failed
        if: ${{ failure() }}
        run: echo fails
  build_artifact:
    runs-on: ubuntu-latest
    needs: [job1]
    steps:
      - run: echo ${{ needs.job1.result }}

No source file or test is named in the issue. Start by reproducing the supplied workflow and inspect the needs.job1.result expression and the toolkit entry point that computes job results. Done means a failed job with continue-on-error set to true is reported as failure through needs.job1.result.