Use content-type fast parse

[blakeembrey]

Preamble: I know fast-content-type-parse is intended to be a Fastify fork of content-type and is likely forked for historical reasons, but I recently released a content-type@2 and the changes seemed relevant to this package. Mostly because there's no need to parse parameters at all.

Changes fast-content-type-parse to use content-type with parameters: false to extract the content-type parameter.

However, the parser in content-type no longer validates during parse (designed to be lenient/fast) so there is a minor behavior change with invalid MIME types. If you sent something like foo it would currently throw during .parse but in this change it'll forward foo along.

Checklist

• run npm run test && npm run benchmark --if-present
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct