Run unit tests (test:unit) in CI on v0.0.x

[imdt-claudiop]

Context

PR #278 (merged into v0.1.x) introduced the initial unit test setup for the data-consumption engine (vitest + testing-library under tests/unit/), and noted as a follow-up that these tests should be wired into the automated CI workflow once we decide to keep them going forward.

PR #279 is the backport of #278 into v0.0.x. It carries the same test suite and the same fix, but the "More" section of the original PR body (which tracked that follow-up) was dropped during backport, so the line v0.0.x currently has no tracking of this gap.

Problem

On v0.0.x, npm run test:unit (vitest) is not invoked by any CI workflow:

• .github/workflows/ts-code-compilation.yml runs npx tsc against the root tsconfig.json (include: ["src/**/*.ts"]), which does not type-check tests/.
• .github/workflows/ts-code-validation.yml runs npm run lint, which does cover tests/, but does not execute the tests.
• No workflow calls test:unit.

As a result, the unit suite introduced by #279 runs only locally and acts as executable documentation, not as a regression gate.

Proposal

Add test:unit to the automated CI on v0.0.x, mirroring whatever pattern the v0.1.x line adopts (or, if v0.1.x has not done it yet, establishing the pattern here). A reference implementation exists in the bbb-plugin-pick-random-user plugin CI.

Related

• Backport PR: [Backport of #278] fix(data-consumption): unsubscribe with current args on unmount & test: initial unit test setup #279
• Original PR (merged, v0.1.x): fix(data-consumption): unsubscribe with current args on unmount & test: initial unit test setup #278
• Sibling core PR: [Backport of #25403] fix(data-consumption): prevent hook usage counter from going negative bigbluebutton#25503