ci: 将 workflow 的 runs-on 改为 internal_docker

自托管 Gitea runner 只注册了 internal_docker 标签，ubuntu-latest 会导致 job 永远排队。

Co-authored-by: Cursor <cursoragent@cursor.com>

tests/ci-parity.test.mjs

@@ -30,6 +30,22 @@ test('both copies of the workflow run the same thing', () => {
   assert.ok(gitea.some((s) => s.includes('--check')), 'neither copy checks the generated files');
 });
 
+test('workflows target the self-hosted runner label', () => {
+  // Gitea act_runner on our instance registers as internal_docker. ubuntu-latest
+  // queues forever because no runner claims it.
+  const workflowPaths = [
+    ['.gitea', 'workflows', 'tests.yml'],
+    ['.github', 'workflows', 'tests.yml'],
+    ['.github', 'workflows', 'release.yml'],
+    ['.github', 'workflows', 'track-upstream.yml'],
+  ];
+  for (const path of workflowPaths) {
+    const yaml = read(...path);
+    assert.match(yaml, /runs-on:\s*internal_docker/, `${path.join('/')} should use internal_docker`);
+    assert.doesNotMatch(yaml, /runs-on:\s*ubuntu-latest/, `${path.join('/')} still asks for ubuntu-latest`);
+  }
+});
+
 test('the workflow does not depend on a runner fetching setup actions', () => {
   // On a self-hosted Gitea, setup-node has to be pulled from GitHub. A node
   // container removes one thing that can be missing on a fresh runner.