[docs] Fix crash on Safari because of unsupported lookahead feature

[cherniavskii]

Fixes #30344

I've followed steps in described in Review suggestion #30107 to run test:e2e-website:dev, but relevant tests kept failing for some reason (even before my changes).
Let me know if there's something missing in the PR.

• I have followed (at least) the PR section of the contributing guide.

[mui-pr-bot]

No bundle size changes

Generated by 🚫 dangerJS against e9d2c02

[oliviertassinari]

I have tried to push the approach further, describing why we have this logic. From what I understand, from an end-user perspective, to mitigate for the first 60 minutes that the crawl index is not up to date, which will lead to people having a 301. From a maintainer perspective, it's about being able to use the search with this feature flag enable.

[oliviertassinari]

@siriwatknp Are you happy with this fix?

[siriwatknp]

@cherniavskii @oliviertassinari thank you so much for the fix. However, I decided to change the migration strategy to another way without replacing the href return from the search result due to the work that I need to do on mui-x repo.

I am closing this PR and remove the logic in #30386

[oliviertassinari]

@siriwatknp Will #30386 be merged before the next release? If there is a chance that it won't, I would suggest that we have a standalone PR to avoid a regression in production once we release HEAD. Currently, HEAD is broken, and production has a hotfix.

[siriwatknp]

we have a standalone PR to avoid a regression

@oliviertassinari good point, maybe reopen and continue on this PR is better.

[siriwatknp]

👍 Thanks for the fix! I have added more tests.

[oliviertassinari]

@siriwatknp Perfect thanks