Issue Description:

A challenge described by Notification Service is: How do I know if a resource was deleted versus not existing in the first place? Their existing logic for polling for deletes will check for a 404 response from the RHOSE API. This is ambiguous in the case of the resource having never been created in the first place.

Acceptance Criteria: 

• Provide a way for customers to be able to determine that a resource was successfully deleted after it was created

Additional Information: 

• One consideration could be the HTTP Gone Response code
• Consideration should be given as to how long the resource appears in the deleted state before being removed.
• Consider if resources that are soft-deleted impact unique constraints e.g does a soft-deleted Bridge prevent another Bridge with the same name being created?