If defining env variables different to the ones from example it fails when checking default

### Current behavior:
I defined variables `CF_TOKEN` and `CF_ZONE` and used them as following:
```
token: ${{ secrets.CF_TOKEN }}
zone: ${{ secrets.CF_ZONE }}
```

And because of the default values are expected as specific names it fails with error:
```
Download action repository 'kriasoft/create-dns-record@v1'
##[error](Line: 22, Col: 14):
##[error](Line: 26, Col: 5): 'default' is already defined
##[error](Line: 22, Col: 14): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.CLOUDFLARE_TOKEN
##[error](Line: 26, Col: 5): 'default' is already defined
##[error]Fail to load /home/runner/work/_actions/kriasoft/create-dns-record/v1/action.yaml
```

### Expected
Any variables can be passed

Start with action.yaml, which the error identifies as failing to load, and inspect how the token and zone inputs define their defaults. Reproduce the action using CF_TOKEN and CF_ZONE instead of the example names. Done means the action loads successfully and accepts arbitrary secret expressions without duplicate-default or hard-coded-name errors.

Written by the indexing model from the issue text.