chore(gatsby-source-wordpress): upgrade file-type

[pieh]

Description

https://github.com/sindresorhus/file-type/releases/tag/v16.0.0 no real breaking changes for us and fixes npm audit alert:

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ high          │ file-type vulnerable to Infinite Loop via malformed MKV file │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ file-type                                                    │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=16.5.4                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ gatsby-source-wordpress                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ gatsby-source-wordpress > file-type                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://www.npmjs.com/advisories/1089123                     │
└───────────────┴──────────────────────────────────────────────────────────────┘

We also already use that version in gatsby-core-utils.

@TylerBarnes could we move from ad-hoc implementation to using createRemoteFileNode from common utility package we have? ( https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-filesystem/src/create-remote-file-node.js ) - that would probably be potential follow up

Documentation

Tests

Related Issues