False positive error for action output

Start by reproducing the reported EA811 diagnostics with the GitHub Actions YAML shown in the issue, then inspect the validator's handling of expressions used in action output assignments. Done means the shown workflow no longer produces false 'output does not exist' errors while genuinely missing outputs remain detectable.

On example on this run:

EA811: action create-featurenet step 5 Called step with id 'get-argocd-featurnet-app-name' output 'name' does not exist
EA811: action create-featurenet step 6 Called step with id 'get-argocd-featurnet-app-name' output 'name' does not exist
EA811: action create-featurenet step 8 Called step with id 'get-argocd-featurnet-app-name' output 'name' does not exist
EA811: action delete-featurenet step 6 Called step with id 'get-argocd-featurnet-app-name' output 'name' does not exist
EA811: action delete-featurenet step 9 Called step with id 'get-argocd-featurnet-app-name' output 'name' does not exist
This error comes from the below code

    - name: Get argocd featurenet app name
      id: get-argocd-featurnet-app-name
      shell: bash
      env:
        # yamllint disable-line rule:line-length
        APP_NAME: ${{ inputs.featurenet-name != '' && inputs.featurenet-name || format('{0}{1}', 'fe-', steps.get-ref-properties.outputs.branch-name-for-argo) }}
      run: |
        echo "name=${{ env.APP_NAME }}" >> $GITHUB_OUTPUT

Most likely problem is that validator sees GH expression and cannot parse name identifier correctly.

The workaround is:

    - name: Get argocd featurenet app name
      id: get-argocd-featurnet-app-name
      shell: bash
      env:
        # yamllint disable-line rule:line-length
        APP_NAME: ${{ inputs.featurenet-name != '' && inputs.featurenet-name || format('{0}{1}', 'fe-', steps.get-ref-properties.outputs.branch-name-for-argo) }}
      run: |
        name_local=${{ env.APP_NAME }}
        echo "name=$name_local" >> $GITHUB_OUTPUT