fix(superset): Exclude superset-ui-switchboard from the frontend SBOM

[dervoeti]

Description

Follow-up to #1616, which fixed 6.0.0 and 6.1.0 but not 4.1.4: https://github.com/stackabletech/docker-images/actions/runs/32719556743

Superset 4.1.4 has a second nested npm project, superset-frontend/packages/superset-ui-switchboard, which ships its own (dependency-less) package-lock.json. cdxgen treats it as an independent project and copies the license string from its package.json verbatim instead of emitting a CycloneDX licenses array, so it rejects its own document and writes no SBOM at all.

Excluding the directory is fine, as the package is a workspace member and stays in the SBOM through the top-level lock file. 6.0.0 and 6.1.0 have no such lock file, so the additional --exclude is a no-op there.

Definition of Done Checklist

Note

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant.

Please make sure all these things are done and tick the boxes

• Changes are OpenShift compatible
• All added packages (via microdnf or otherwise) have a comment on why they are added
• Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
• All packages should have (if available) signatures/hashes verified
• Add an entry to the CHANGELOG.md file
• Integration tests ran successfully

TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>

See the output of boil to retrieve the image manifest URI for <MANIFEST_URI>.