fix: add missed JPEG file extensions to KNOWN_ASSET_TYPES

[cawa-93]

Description

Add more JPEG file extensions to KNOWN_ASSET_TYPES. I get extensions from MDN https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types

---

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.
• Read the Pull Request Guidelines and follow the Commit Convention.
• 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).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

mrmime(ext) returns undefined for these extensions.
So if these files were inlined, I suppose it will become data:undefined;base64,content.

vite/packages/vite/src/node/plugins/asset.ts

Line 342 in 09648c2

url = `data:${mrmime.lookup(file)};base64,${content.toString('base64')}`

> require('mrmime').lookup('.jfif')
undefined
> require('mrmime').lookup('.pjpeg')
undefined
> require('mrmime').lookup('.pjp')
undefined

It seems there are some other extensions which have the same problem. (.ico is ok)

> require('mrmime').lookup('.ico')
undefined
> require('mrmime').lookup('.flac')
undefined
> require('mrmime').lookup('.aac')
undefined
> require('mrmime').lookup('.eot')
undefined

[sapphi-red]

As there are some extensions which is lacking mime data, I will create a PR after this PR was merged.