fix: point stream-labs references at the streamlabs org

[nbarrett-logitech]

What

Points every stream-labs GitHub reference in this repo at the streamlabs org.

Why

Streamlabs renamed its GitHub organization from stream-labs to streamlabs. GitHub keeps 301 redirects from the old namespace, but only until somebody claims that namespace and creates a repository with a matching name. At that point the redirect stops resolving and the URL points at their repository instead.

The stream-labs namespace is no longer under our control. It is currently held by an organization created on 2026-08-23 that has no public repositories, which is the only reason the redirects still resolve today. They break as soon as a matching repository name is created there.

Tracked as HackerOne #3065731 (Critical).

Impact

This workflow checks out stream-labs/symsrv-scripts and then executes ./symsrv-scripts/main.bat, in a job that has the symbol-server AWS credentials in its environment. That checkout resolves only through the rename redirect. If the redirect breaks, the job runs code from a repository we do not control, with those credentials in scope.

The -repo_userId value is a separate issue in the same file: it is passed through to github-sourceindexer.ps1 and written into the generated PDBs as the source-fetch URL, so published debug symbols currently direct debuggers at the old namespace.

Also in this PR — two more build-time fetches through the old namespace

Found while sweeping the rest of the repo, and they belong to the same class as the workflow issue rather than to cosmetic metadata:

1. CMake fetches and runs a script from the old namespace.

FetchContent_Declare(deps_checker URL
  "https://raw.githubusercontent.com/stream-labs/obs-studio-node/staging/dependency_checker/check_dependencies.cmd")

raw.githubusercontent.com resolves the old org name directly — verified, it returns HTTP 200 with no redirect hop. So if a repository named obs-studio-node appears under the stream-labs namespace, this fetch starts serving that file, and the build executes it.

2. Repository metadata — package.json repository/bugs/homepage URLs and, where present, CHANGELOG links. Cosmetic, but they are what people copy clone commands out of.