fix(deps): switch to using the "content-type" package for content type parsing (#807)

Author: blakeembrey

package-lock.json

@@ -28,6 +28,7 @@
     "@octokit/endpoint": "^11.0.3",
     "@octokit/request-error": "^7.0.2",
     "@octokit/types": "^16.0.0",
+    "content-type": "^2.0.0",
     "fast-content-type-parse": "^3.0.0",
     "json-with-bigint": "^3.5.3",
     "universal-user-agent": "^7.0.2"

package.json

@@ -1,11 +1,9 @@
-import { safeParse } from "fast-content-type-parse";
+import { parse, type ContentType } from "content-type";
 import { JSONParse, JSONStringify } from "json-with-bigint";
 import { isPlainObject } from "./is-plain-object.js";
 import { RequestError } from "@octokit/request-error";
 import type { EndpointInterface, OctokitResponse } from "@octokit/types";
 
-type ContentType = ReturnType<typeof safeParse>;
-
 /* v8 ignore next -- @preserve */
 const noop = () => "";
 
@@ -162,7 +160,7 @@ async function getResponseData(response: Response): Promise<any> {
     return response.text().catch(noop);
   }
 
-  const mimetype = safeParse(contentType);
+  const mimetype = parse(contentType);
 
   if (isJSONResponse(mimetype)) {
     let text = "";