Bug 1290783

Description of problem:
When you perform delete action twice for the same tag, you get the incorrect second response 204, should be 404
The same case when you perform the delete method via post request for non existent tag.

Version-Release number of selected component (if applicable):
5.5.0.13

How reproducible:
Always

Steps to Reproduce:
First case:
1. Call delete method for any tag from tags collection a few times
 https://ip_address/api/tags/<tag_id> {'action': u'delete'}
2. Check the responses

Second case:
1. Call post method for tags collection
https://ip_address/api/tags 
{'action': u'delete', 'resources': [{'href': 'https://ip_address/api/tags/<tag_id>'}]} 
<tag_id> choose non existent id, for example 20000
2. Check the response

Actual results:
You get 204 response code and it doesn't matter how many time you are going to perform delete method for the same tag

Expected results:
First case:
You should get 404 response code at second attempt to delete tag, that server has not found anything matching the URI given, because the tag with <tag_id> specified in the request should be deleted.

Second case: 
You should get 404 response code, that server has not found anything matching the URI given, because tag with such id doesn't exist.

Additional info:
Other collections have the behavior described in Expected Result.