Category field added in obligation (get, post, patch)

[bhowmik94]

Changes

• Add category field for obligation GET, POST, PATCH requests

• Add category for obligation import & export requests

• Validate the field values for the given enum types.

• Fixes New field "Category" in obligations GET, PUT, POST  #85

Submitter Checklist

• Includes tests (if there is a feature changed/added)
• Includes docs ( if changes are user facing)
• I have tested my changes locally.

References

[GMishx]

@bhowmik94 you need to commit the updated doc files after the swag init and swag fmt

[GMishx]

@bhowmik94 make sure to update the PR description when you are creating one.

[GMishx]

Tried adding category to an existing obligation and it failed.

curl -X 'PATCH' \
  'http://localhost:8085/api/v1/obligations/my%20obligation' \
  -H 'accept: application/json' \
  -H 'Authorization: my.token' \
  -H 'Content-Type: application/json' \
  -d '{
"category": "Distribute"
}'

The response is 200

{
  "status": 200,
  "data": [
    {
      "id": 1,
      "topic": "",
      "type": "",
      "text": "",
      "classification": "",
      "modifications": false,
      "comment": "",
      "active": false,
      "text_updatable": false,
      "category": ""
    }
  ],
  "paginationmeta": {
    "resource_count": 1
  }
}

[bhowmik94]

@GMishx Kindly try the update request now.

[GMishx]

Please check the category value against the allowed values from the enums:"Distribution,Patent,Internal,Contractual,Export Control,General". Currently I can put any values in the field with a PATCH or a POST request.

Also, the export and import endpoints do not reflect this new field. Please fix it as well.

And please update the PR description!