/create endpoint: accept an "entry object" instead of a 2-element array

[dcastro]

This issue is blocked by https://github.com/serokell/coffer/pull/37.

Clarification and motivation

Right now the /create endpoint takes a json object with a 2-element array. The 1st element is a json object containing public fields, and the 2nd element is another json object containing private fields.

The rest of the entry's info is in the query string.

Example:

curl -s -D /dev/stderr \
  -H 'token: root' \
  'localhost:8081/api/v1/content/create?path=/ex1&force&tag=tag1&tag=tag2' \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '[{"some-public-field": "a"}, {"some-private-field": "b"}]' | jq

Instead, the endpoint should accept a json object representing the entire "Entry" entity, e.g.

{
  "path": "/ex1",
  "fields": {
    "some-public-field": {
      "contents": "a",
      "visibility": "public"
    },
    "some-private-field": {
      "contents": "b",
      "visibility": "private"
    }
  },
  "tags": [
    "tag1",
    "tag2"
  ]
}

Acceptance criteria

• The /create endpoint accepts a json object representing the "Entry" entity

[sancho20021]

• Should /create endpoint accept qualified path as a parameter?
  • If so, do we need any path inside Entry json at all?
• What is the most suitable file to put new Entry datatype in (for passing as JSON)?