build for production: icon within noscript will not be relocated (index.html)

[AHorak]

Describe the bug

As you can see there is one on the noscript and the other one outside.
The one outside will be "relocated" from src/assets/favicon.svg to /assets/favicon-c725382f.svg

See the snippet from index.html of my react application.

Before building for production:

<noscript>
        <div style="position: fixed; margin: 0px auto;  top: 50%; left: 50%; transform: translate(-50%, -50%); z-index: 30000000"; text-align: center">
            <img src="src/assets/favicon.svg" width="64" height="64" style="display:block; margin: 0px auto">
            <p><b>You need to enable JavaScript to run this app.</b></p>
        </div>
    </noscript>
    <img src="src/assets/favicon.svg" width="64" height="64" style="display:block; margin: 0px auto">

---

After:

<noscript>
        <div style="position: fixed; margin: 0px auto;  top: 50%; left: 50%; transform: translate(-50%, -50%); z-index: 30000000"; text-align: center">
            <img src="src/assets/favicon.svg" width="64" height="64" style="display:block; margin: 0px auto">
            <p><b>You need to enable JavaScript to run this app.</b></p>
        </div>
    </noscript>
    <img src="/assets/favicon-c725382f.svg" width="64" height="64" style="display:block; margin: 0px auto">

Reproduction

?

Steps to reproduce

add noscript to your index.html with one img inside.

yarn run build vite

System Info

Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 109.0.5414.75
    Edge: Spartan (44.19041.1266.0), Chromium (109.0.1518.55)
    Internet Explorer: 11.0.19041.1566

Used Package Manager

yarn

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.