refactor(core-utils): use JSON.parse instead of fast-json-parse

[faustbrian]

Removes the fast-json-parse module because it's no longer necessary.

[alessiodf]

Suggested change

	body: JSON.parse(body || {}),
	body: JSON.parse(body || "{}"),

JSON.parse expects a string, not an object, otherwise you'll get a SyntaxError as it will try to parse [object Object] from {}.toString().

[alessiodf]

Suggested change

	body: JSON.parse(error.response.body || {}),
	body: JSON.parse(error.response.body || "{}"),

JSON.parse expects a string, not an object, otherwise you'll get a SyntaxError as it will try to parse [object Object] from {}.toString().

[alessiodf]

I know the latest commit is only a wip so you might be aware of this already but I'm mentioning it here just in case as it will introduce some undesired effects with the api in its current incarnation.

[alessiodf]

Suggested change

	body: JSON.parse(body),
	body: JSON.parse(body || "{}"),

Alternatively (might be more performant):

Suggested change

	body: JSON.parse(body),
	body: body ? JSON.parse(body) : {},

In its current state it will throw if body is empty or undefined since parsing will fail, which is always the case when the response is to a HEAD request. In real terms this means port pinging in the peer communicator will set all port values to -1 in the /api/peers endpoint.

[alessiodf]

Suggested change

	body: JSON.parse(error.response.body),
	body: JSON.parse(error.response.body || "{}"),

Same.