fix(html): skip inlining icon and manifest links

[bluwy]

Description

fix #6741
fix #5962

Don't inline icon and manifest <link>s. The above issues explained why, but to summarize:

1. Icons are low-priority-fetched by browsers, so they should be links. Otherwise user would always fetch them because it's inlined.
2. Manifest files can't be inlined, it always needs a url.

Additional context

I'm also partially working towards supporting import img from './foo.png?inline=false (as a poc and we could also further discuss), this is a cutoff point for now to fix those issues.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines, especially the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Update the corresponding documentation if needed.
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

💚

[bluwy]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on aa6d828: Open

suite	result	latest scheduled
analogjs	✅ success	✅ success
astro	✅ success	✅ success
histoire	✅ success	✅ success
ladle	✅ success	✅ success
laravel	❌ failure	❌ failure
marko	✅ success	✅ success
nuxt	❌ failure	❌ failure
nx	✅ success	✅ success
previewjs	✅ success	✅ success
qwik	✅ success	✅ success
rakkas	✅ success	✅ success
sveltekit	✅ success	✅ success
unocss	✅ success	✅ success
vike	✅ success	✅ success
vite-plugin-pwa	✅ success	✅ success
vite-plugin-react	✅ success	✅ success
vite-plugin-react-pages	✅ success	✅ success
vite-plugin-react-swc	✅ success	✅ success
vite-plugin-svelte	✅ success	✅ success
vite-plugin-vue	✅ success	✅ success
vite-setup-catalogue	✅ success	✅ success
vitepress	✅ success	✅ success
vitest	✅ success	✅ success

[slyshykO]

Why did you remove this feature rather than add an option to the configuration?
Why did you do this on a minor release?
Is it possible to return to the old behaviour?

[bluwy]

Can you explain why you need the old behaviour? The previous behaviour was a bug.

[slyshykO]

Can you explain why you need the old behaviour? The previous behaviour was a bug.

I am developing a web configurator for an embedded device. So I don't need a performance for multiple downloads, cashing, etc. Also, I embed the built page in the configurator executable and receive a single file that contains everything. All files that are not inlined separately should be processed on the side of my configurator. So, it just adds work on my side.
I don't see any issues if inlining will be manipulated through options.

[bluwy]

Thanks for explaining your usecase. Since it isn't Vite's main target audience, I think the PR still make sense. It'll be beneficial for many websites ootb. That means you're required to inline the favicon yourself in this case. Vite will only add options when really only needed: https://vitejs.dev/guide/philosophy.html#lean-extendable-core

[ArnaudBarre]

For info if #15366 lands you should be able to overwrite this change (exact implementation still to be discussed)

[lapo-luchini]

For info if #15366 lands you should be able to overwrite this change

Doesn't seem to be able to force inlining.