Rewrite API to parse JSON content body in POST and DELETE requests

[db-2001]

• Added API documentation
  Gonna leave this as draft until I verify all the API calls work properly.
  Addresses Rewrite API to use JSON Content Body #144

[C9Glax]

Looks more readable than mine.
Left a few things I would improve, but other than that, looks ready to merge (since the old uri-method can still be used)

[C9Glax]

Can have an optional body, to get a specific job

{
jobId: ${Tranga Job ID}
}

See

tranga/Tranga/Server.cs

Lines 172 to 176 in 5f03b0d

	if(!_parent.jobBoss.jobs.Any(jjob => jjob.id == jobId))
	SendResponse(HttpStatusCode.BadRequest, response);
	else
	SendResponse(HttpStatusCode.OK, response, _parent.jobBoss.jobs.First(jjob => jjob.id == jobId));
	break;

[C9Glax]

I can't think of a good reason why we should split Parameters and Body...

[C9Glax]

It's all getting thrown into the same Dictionary, so having a key-value table sounds like a better idea.

[db-2001]

Yeah I agree, I'll just make them the same dictionary if that's what you meant

[C9Glax]

I mean in the md file you don't have to split them into "Parameters" and "Request Body"

[db-2001]

Ah, okay, I was kinda following the Kacita API docs guide, but yeah

[C9Glax]

{
	"jobId": ${Tranga Job ID}
}

[C9Glax]

optional, to just update a single manga

{
internalId: ${Tranga Manga ID}
}

[C9Glax]

when left empty, resets it to the default

[C9Glax]

Probably want a try-catch so we dont crash every time we get a request that has for example integers, booleans, arrays, or nested objects.

[db-2001]

Good call