ooo: Request textDocument/completion failed with message: Maximum call stack size exceeded: Error: Request textDocument/completion failed with message: Maximum call stack size exceeded

**Describe the bug**

Extension is running out of memory sometimes:

```
2024-07-31 13:08:28.569 [error] Request textDocument/completion failed with message: Maximum call stack size exceeded: Error: Request textDocument/completion failed with message: Maximum call stack size exceeded
at /Users/ssbarnea/.vscode/extensions/github.vscode-github-actions-0.26.3/dist/extension-node.js:2:633457
at /Users/ssbarnea/.vscode/extensions/github.vscode-github-actions-0.26.3/dist/extension-node.js:2:633751
at Timeout._onTimeout (/Users/ssbarnea/.vscode/extensions/github.vscode-github-actions-0.26.3/dist/extension-node.js:2:634113)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
2024-08-01 13:33:57.033 [error] [Extension Host] Error loading yaml file
```

**To Reproduce**
Steps to reproduce the behavior:
1. With this workflow '...'
2. Do this '...'
3. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Extension Version**
`v0.26.3`

**Additional context**

That is on a 64GB M1 max laptop, so bit unexpected. I wonder if that is caused by node running out of memory as I encountered recently another issue with it that required me to add `NODE_OPTIONS=--max-old-space-size=4096` in order to just run `yarn webpack`... :p

Start with the textDocument/completion failure and the YAML-loading error reported in the stack trace from dist/extension-node.js. Reproduce the issue with a real workflow, since the report's reproduction steps are placeholders, then trace the completion request until the call-stack or memory growth is identified. Done means completion no longer exceeds the call stack and YAML files load successfully.

Written by the indexing model from the issue text.