fix: pin luxon to fix build

[dervoeti]

Description

Building Superset 4.1.2 and 4.1.4 currently fails.

For some reason, npm tries to use a newer version of luxon than the version in the lock file. I suspect this might be related to how npm before version 11 handles workspace dependencies in lock files, some dependencies do not seem to be locked. When I create the lock file with npm 11, way more dependencies are locked. I decided not to commit the lock file generated by npm 11 though, because the diff would be huge and some package versions would have changed. That's why the luxon version is set to 3.6.1 now to prevent npm from trying to select a newer version, so that the same packages as in the original Superset build are used and building works again, without changing too much. We can reconsider another fix for this if this happens again.

Local build succeeded and smoke test passed.

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>.

[sbernauer]

Sounds like a mess :)