Bug Report: ChunkLoadError when loading lazy-loaded frontend bundle

### Bug description

Superset displays an "Unexpected error" page with the following error:

ChunkLoadError: Loading chunk 4169 failed.

The application fails while attempting to load a lazily loaded frontend bundle, resulting in a broken UI and preventing access to the affected page.

```
Unexpected error
ChunkLoadError: Loading chunk 4169 failed.

Lazy
l@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1116:190
98837/g/<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7054
main
2672/h1<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:340:4725
98837/g/<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7054
div
2672/h2<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:340:4989
Suspense
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:20127
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:20770
tD@http://127.0.0.1:8088/static/assets/spa.72ab05fb3acc832bdf24.entry.js:301:8750
R@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:7:873
n@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:93148
x@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:7:1072
e3@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1501:3086
c@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1412:2136
79551/s<@http://127.0.0.1:8088/static/assets/2290.4aef28ca85361c2fdbd3.entry.js:273:13694
C@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:554:29987
rd@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:8092
rv@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:9872
rb@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:13885
y@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7234
SupersetThemeProvider@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1:3726
i@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1541:18426
tH@http://127.0.0.1:8088/static/assets/spa.72ab05fb3acc832bdf24.entry.js:301:9615
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:17228
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:8222
tW
See less

```

I verified that Superset is serving static assets correctly.

For example, opening the following asset directly in the browser returns the JavaScript file successfully:

http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js

The file is accessible and downloads/loads without error.

Despite this, the application still throws:

ChunkLoadError: Loading chunk 4169 failed.

### Screenshots/recordings

_No response_

### Superset version

master / 6.1

### Python version

3.11

### Node version

20

### Browser

Chrome

### Additional context

_No response_

### Checklist

- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Start by reproducing the failure on the affected Superset page and inspect the lazy-loaded bundle request for chunk 4169 alongside the referenced static assets, including 8115.ef2c25320df8c6b15d8a.entry.js and vendors.6f4ecbc3d2e23e236060.entry.js. Done means the affected page loads without the ChunkLoadError in Chrome and the relevant bundle remains accessible when requested directly.

Written by the indexing model from the issue text.