Unrecognized Github Actions Secret Context

**Describe the bug**
- I have a GitHub Actions workflow, VSCode recommended me the Extension.
- And i use the Environment Feature for GitHub Action Secrets.
- This is not recognized by the Extension,
- even that the Environment Secrets works when i let the Action run.
- Even more frustrating:
- there seems to be no option to ignore or comment out that warning that the secret isn't valid
- we need an option to ignore that if the Extension fails to read the environment context

**To Reproduce**
Steps to reproduce the behavior:
1. The beginning of the Jobs YAML:

jobs:
test:
runs-on: ubuntu-latest
environment: TWITCH-DOWNLOADER
...

2. The Step that Uses the Secrets:
- name: Schreibe Secrets in .env-Datei
run: |
echo "TWITCH_CLIENT_ID=${{ secrets.TWITCH_CLIENT_ID }}" >> .env
echo "TWITCH_CLIENT_SECRET=${{ secrets.TWITCH_CLIENT_SECRET }}" >> .env

The Repo itself private, but i guess the error is easy to reproducible with
- create a repo
- creating a environment with that name (in https://github.com/(user)/(repo)/settings/secrets/actions)
- creating 2 Secrets named like that in that environment
- creating a github action yaml file with just that step above
- Save
- The Yaml loaded into VSCode with the GitHub Actions Extension running
X the Secrets will be recognized as missing or not defined X

**Expected behavior**
To recognize the Environment and the Secrets in there

Start by reproducing the warning with the provided jobs YAML, an environment named TWITCH-DOWNLOADER, and the two environment secrets referenced in the workflow. Trace how the GitHub Actions Extension validates secrets and environment context; done means the environment secrets are recognized without a missing-or-undefined warning.

Written by the indexing model from the issue text.