title: Secret interpolation is giving syntax error in caller workflow when calling a resusable workflow in GitHub Action
body: <p>I am using <a href="https://docs.github.com/en/actions/learn-github-actions/reusing-workflows" rel="nofollow noreferrer">reusable workflow</a> and when passing a <code>secrets</code> from caller workflow to reusable workflow, I am getting following syntax error:</p>
  <pre class="lang-sh prettyprint-override"><code>The workflow is not valid. .github/workflows/caller_workflow.yml (Line: 28, Col: 28): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.SECRET_1 .github/workflows/caller_workflow.yml (Line: 29, Col: 22): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.SECRET_2
  </code></pre>
  <p>Not sure why the interpolation is not working.</p>
  <p><strong>This is my caller workflow <code>caller_workflow.yml</code>(giving above error):</strong></p>
  <pre><code>name: Build workflow
  on:
    push:
      branches:
        - dev
        - main
    pull_request:
      types:
        - opened
        - edited
        - reopened
      branches:
        - main
        - dev
  
  jobs:
    # reference: https://docs.github.com/en/actions/learn-github-actions/reusing-workflows#example-caller-workflow
    org-checks:
      uses: repo/.github/workflows/main_workflow.yml@main
      with:
        SECRET_1: ${{ secrets.SECRET_1 }}
        SECRET_2: ${{ secrets.SECRET_2 }}
  </code></pre>
  <p><strong>This is my reusable workflow:</strong></p>
  <pre class="lang-yaml prettyprint-override"><code>name: CI workflow
  on:
    workflow_call:  # enables this workflow to be reusable for other repo
      secrets:
        SECRET_1:
          description: 'secret 1'
        SECRET_2:
          description: 'secret 2'
    push:
      branches:
        - main
    pull_request:
      types:
        - opened
        - edited
        - reopened
      branches:
        - main
  
  jobs:
    job-name-to-run:
         ...... ......
  
  </code></pre>
  <p>secrets in other flow are working all fine with the same syntax.</p>