feat: Update mimeType extensions from mime-db v1.52.0

[franznoel]

Description

Updated the mimeTypes list of system coming from mime-db v1.52.0

Taken from this list: https://github.com/jshttp/mime-db/blob/v1.52.0/db.json

[ST-DDT]

Please also update the version number in the jsdocs.

[franznoel]

Please also update the version number in the jsdocs.

How should I update the jsdocs version? Is there a contributing guide?

[codecov]

Codecov Report

Merging #535 (35adc77) into main (e643835) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             main     #535     +/-   ##
=========================================
  Coverage   99.33%   99.34%             
=========================================
  Files        1923     1923             
  Lines      176857   178815   +1958     
  Branches      908      908             
=========================================
+ Hits       175687   177645   +1958     
  Misses       1114     1114             
  Partials       56       56             

Impacted Files	Coverage Δ
src/locales/en/system/mimeTypes.ts	100.00% <ø> (ø)

[ST-DDT]

update the version number

How should I update the jsdocs version?

I'm referring to this line:

faker/src/locales/en/system/mimeTypes.ts

Line 25 in 1058e17

Definitions from mime-db v1.21.0

Please update it to the exact tag-name (version) of the commit you used to import the db from.

I assume it's https://github.com/jshttp/mime-db/releases/tag/v1.52.0 .

[HonzaMac]

I would love to see this out in next version, how can I help with this?

[ST-DDT]

@Shinigami92 IMO this is a c: locale and thus can be merged in v6.1.

[Shinigami92]

Could you order this extList and remove the duplicate mpeg?
Then we have less conflicts in the future.

[Shinigami92]

@Shinigami92 IMO this is a c: locale and thus can be merged in v6.1.

All c: locale are currently target for v6.2: https://github.com/faker-js/faker/pulls?q=is%3Aopen+is%3Apr+label%3A%22c%3A+locale%22
Why handle this PR differently?

[HonzaMac]

We use mime-types for input validation (which use mimedb inside). Problem is that faker generates extensions i.e. mbp which was renamed later, but it fails our suites sometimes when Faker generate it. Faker have mimedb from 2016.

And because its not dependency, I cant override it in yarn resolves.

[ST-DDT]

This PR needs to be rebased/updated.

[prisis]

I have a different approach #808

[ST-DDT]

Superseded by #808 . Thanks for your contribution.