build(deps): bump swagger-ui-react from 4.1.3 to 5.17.2 in /docs

[dependabot[bot]]

Bumps swagger-ui-react from 4.1.3 to 5.17.2.

Release notes

Sourced from swagger-ui-react's releases.

Swagger UI v5.17.2 Released!

5.17.2 (2024-04-25)

Bug Fixes

• config: remove system config source (#9875) (333e5e3), closes #5148
• allow to create SwaggerUI instances without rendering to the DOM container by default

Swagger UI v5.17.1 Released!

5.17.1 (2024-04-24)

Bug Fixes

• json-schema-2020-12-samples: skip anyOf and oneOf while merging schemas (#9853) (f7373a0), closes #9198
• utils: fix validation for required values without specified type (#9863) (6fccf9e), closes #8007
• deps: eliminate runtime errors related to traverse library
• upstream fixes in swagger-client (v3.27.1, v3.27.2)

Swagger UI v5.17.0 Released!

5.17.0 (2024-04-22)

Features

• config: expose config and make it overridable (#9862) (17d50a6)
• swagger-ui-react: rewrite into SSR compatible function component (#9855) (351191b), closes #9243

Swagger UI v5.16.2 Released!

5.16.2 (2024-04-19)

Bug Fixes

• swagger-ui-react: avoid triggering implicit system rendering (#9847) (3a671c6), closes #9846

Swagger UI v5.16.1 Released!

5.16.1 (2024-04-18)

Bug Fixes

• config: add options defined during runtime (#9845) (60670d1), closes #9844
• config: address getting configUrl from options (#9840) (dc9650b), closes #9819
• config: sync SwaggerUI default options with swagger-ui-react (#9843) (bcd7388), closes #9838

Swagger UI v5.16.0 Released!

5.16.0 (2024-04-18)

... (truncated)

Commits

• a88cce2 chore(release): cut the v5.17.2 release
• 333e5e3 fix(config): remove system config source (#9875)
• 636c352 chore(deps): bump dependabot/fetch-metadata from 2.0.0 to 2.1.0 (#9872)
• 76495e8 chore(deps-dev): bump @​commitlint/cli from 19.2.2 to 19.3.0 (#9871)
• 0fc96ce chore(release): cut the v5.17.1 release
• f7373a0 fix(json-schema-2020-12-samples): skip anyOf and oneOf while merging schemas ...
• dee2ad0 chore(deps): bump swagger-client from 3.27.0 to 3.27.2 (#9868)
• 4228d84 chore(deps-dev): bump postcss-preset-env from 9.5.8 to 9.5.9 (#9867)
• 6fccf9e fix(utils): fix validation for required values without specified type (#9863)
• cf7b769 chore(deps-dev): bump postcss-preset-env from 9.5.6 to 9.5.8 (#9861)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[HertzDevil]

Manually linking all the libraries in said install directory to the same path as the symlinks in the target directory also gets the executable to work.

Since the compiler itself is dynamically linked, this would now be expected from a complete installation, so yes, the tool has to symlink all the DLLs as well (automatically).

[straight-shoota]

Ah, so nowadays we have no influence on where DLLs are looked up, right? They need to be in PATH. Only the original delay load implementation (with -Dpreview_dll from #13436) in the Crystal runtime we could accomodate to lookup in the real path of the executable.

[devnote-dev]

If there's no real use case for this functionality then I will update Crimson to symlink all DLLs too, but my understanding of the DLL search order was that the path of the executable is included if not the first location to look, and in this case the symlink path isn't the executable path.