Problem: uPortal-Project/uPortal#2982 fixed a regression in
common.less where an @import path no longer existed in the
Bootstrap 5 webjar, breaking lessc compilation for any custom
skin scaffolded by :overlays:uPortal:skinGenerate. Without an
automated check, the next break of common/common.less only
surfaces when a deployer runs tomcatDeploy in their own
environment and notices missing CSS.

Goal: pin the regression with a Playwright test that exercises
the full scaffold-and-compile path (skinGenerate -> tomcatDeploy
-> lessc) on every playwrightRun.

Changes:
- overlays/uPortal/build.gradle: new playwrightSkinFixture task
  that idempotently regenerates the playwrightSkin scaffold from
  etc/skin/ and ensures a <skin> entry exists in skinList.xml;
  scaffold-template drift is caught even when the skin files are
  committed, because the fixture overwrites them on every run
- gradle/tasks/playwright.gradle: playwrightRun now depends on
  playwrightSkinFixture and :overlays:uPortal:tomcatDeploy;
  ordering enforced via prepareSkinResources.mustRunAfter(
  playwrightSkinFixture) inside gradle.projectsEvaluated to avoid
  eager cross-project configuration of :overlays:uPortal at root
  evaluation time
- overlays/uPortal/src/main/webapp/media/skins/respondr/: commit
  the generated playwrightSkin.less, playwrightSkin/, and a
  skinList.xml entry so the skin-compile chain in
  overlays/uPortal/build.gradle (which evaluates the fileTree at
  configuration time) registers compileLess for our skin; the
  fixture overwrites these on every run
- tests/ux/skin/custom-skin.spec.ts: assert
  /uPortal/media/skins/respondr/playwrightSkin.css returns 200,
  has >500 bytes, and contains a Bootstrap marker (--bs-, .btn,
  or @import bootstrap.css) — proves common.less's @import
  resolved. Pre-fix code fails compileLess0 before the spec runs;
  post-fix the spec passes

Notes: scoped to compile-only coverage (Shape 1) rather than
driving the dynamic-respondr-skin or stylesheet-descriptor
default-skin switch path, since the PR #2982 regression is at
lessc compile time. Activation testing is left for a follow-up if
the dynamic skin path needs its own regression guard. Skin name
"playwrightSkin" deliberately distinct from "test" so a developer
can keep their own scaffold-named "test" skin alongside the
fixture's.

Problem: uPortal-Project/uPortal#2982 fixed a regression in
common.less where an @import path no longer existed in the
Bootstrap 5 webjar, breaking lessc compilation for any custom
skin scaffolded by :overlays:uPortal:skinGenerate. Without an
automated check, the next break of common/common.less only
surfaces when a deployer runs tomcatDeploy in their own
environment and notices missing CSS.

Goal: pin the regression with a Playwright test that exercises
the full scaffold-and-compile path (skinGenerate -> tomcatDeploy
-> lessc) on every playwrightRun.

Changes:
- overlays/uPortal/build.gradle: new playwrightSkinFixture task
  that idempotently regenerates the playwrightSkin scaffold from
  etc/skin/ and ensures a <skin> entry exists in skinList.xml;
  scaffold-template drift is caught even when the skin files are
  committed, because the fixture overwrites them on every run
- gradle/tasks/playwright.gradle: playwrightRun now depends on
  playwrightSkinFixture and :overlays:uPortal:tomcatDeploy;
  ordering enforced via prepareSkinResources.mustRunAfter(
  playwrightSkinFixture) inside gradle.projectsEvaluated to avoid
  eager cross-project configuration of :overlays:uPortal at root
  evaluation time
- overlays/uPortal/src/main/webapp/media/skins/respondr/: commit
  the generated playwrightSkin.less, playwrightSkin/, and a
  skinList.xml entry so the skin-compile chain in
  overlays/uPortal/build.gradle (which evaluates the fileTree at
  configuration time) registers compileLess for our skin; the
  fixture overwrites these on every run
- tests/ux/skin/custom-skin.spec.ts: assert
  /uPortal/media/skins/respondr/playwrightSkin.css returns 200,
  has >500 bytes, and contains a Bootstrap marker (--bs-, .btn,
  or @import bootstrap.css) — proves common.less's @import
  resolved. Pre-fix code fails compileLess0 before the spec runs;
  post-fix the spec passes

Notes: scoped to compile-only coverage (Shape 1) rather than
driving the dynamic-respondr-skin or stylesheet-descriptor
default-skin switch path, since the PR #2982 regression is at
lessc compile time. Activation testing is left for a follow-up if
the dynamic skin path needs its own regression guard. Skin name
"playwrightSkin" deliberately distinct from "test" so a developer
can keep their own scaffold-named "test" skin alongside the
fixture's.

Problem: uPortal-Project/uPortal#2982 fixed a regression in
common.less where an @import path no longer existed in the
Bootstrap 5 webjar, breaking lessc compilation for any custom
skin scaffolded by :overlays:uPortal:skinGenerate. Without an
automated check, the next break of common/common.less only
surfaces when a deployer runs tomcatDeploy in their own
environment and notices missing CSS.

Goal: pin the regression with a Playwright test that exercises
the full scaffold-and-compile path (skinGenerate -> tomcatDeploy
-> lessc) on every playwrightRun.

Changes:
- overlays/uPortal/build.gradle: new playwrightSkinFixture task
  that idempotently regenerates the playwrightSkin scaffold from
  etc/skin/ and ensures a <skin> entry exists in skinList.xml;
  scaffold-template drift is caught even when the skin files are
  committed, because the fixture overwrites them on every run
- gradle/tasks/playwright.gradle: playwrightRun now depends on
  playwrightSkinFixture and :overlays:uPortal:tomcatDeploy;
  ordering enforced via prepareSkinResources.mustRunAfter(
  playwrightSkinFixture) inside gradle.projectsEvaluated to avoid
  eager cross-project configuration of :overlays:uPortal at root
  evaluation time
- overlays/uPortal/src/main/webapp/media/skins/respondr/: commit
  the generated playwrightSkin.less, playwrightSkin/, and a
  skinList.xml entry so the skin-compile chain in
  overlays/uPortal/build.gradle (which evaluates the fileTree at
  configuration time) registers compileLess for our skin; the
  fixture overwrites these on every run
- tests/ux/skin/custom-skin.spec.ts: assert
  /uPortal/media/skins/respondr/playwrightSkin.css returns 200,
  has >500 bytes, and contains a Bootstrap marker (--bs-, .btn,
  or @import bootstrap.css) — proves common.less's @import
  resolved. Pre-fix code fails compileLess0 before the spec runs;
  post-fix the spec passes

Notes: scoped to compile-only coverage (Shape 1) rather than
driving the dynamic-respondr-skin or stylesheet-descriptor
default-skin switch path, since the PR #2982 regression is at
lessc compile time. Activation testing is left for a follow-up if
the dynamic skin path needs its own regression guard. Skin name
"playwrightSkin" deliberately distinct from "test" so a developer
can keep their own scaffold-named "test" skin alongside the
fixture's.