`PUT /entities/items/{item_id}/labels/{language_code}`
`PUT /entities/items/{item_id}/description/{language_code}`
Request Payload
```
label: LABEL-TEXT
(optional) comment: Edit comment
(optional) tags: Edit tags (array/list)
(optional) bot: true/false
```
The respective successful responses should present the relevant data as a string -- similar to the responses of `GET /entities/items/{item_id}/labels/{language_code}`, and `GET /entities/items/{item_id}/descriptions/{language_code}` respectively.
Cases to consider:
- if {item_id} does not exist, the API should generate a 404 response `{ "code": "item-not-found", "message": "Could not find an item with the ID: {item_id}" }`
- if {item_id} is not a valid item ID, the API should generate a 400 response `{ "code": "invalid-item-id", "message": "Not a valid item ID: {item_id}"} `
- if {language_code} is not a valid language code, the API should generate a 400 response `{ "code": "invalid-language-code", "message": "Not a valid language code: {language_code}"} `
- if {item_id} is a redirect, the API should generate a 409 response `{ "code": "redirected-item", "message": "Item {item_id} has been merged into {other_id}." }`
- TODO: invalid label/description
- If an invalid Mediawiki edit tag is provided, the API should generate a 400 response `{ "code": "invalid-edit-tag", "message": "Invalid MediaWiki tag: {tag}"} `
- If a value for `bot` parameter other than `true` or `false`is provided, Mediawiki REST API framework's error is to be used