delete the RIM from the backend table when /delete is called instead of archiving
if an archived RIM is returned for FW validation then attempt to return an unarchived RIM with matching identifiers.
This PR also attempted to address the use cases where a good or bad RIM bundle is sent with an initial provision and then replaced by the other. This grew beyond the scope of this PR and will be handled in a future issue.
The two main changes included here are:
This PR also attempted to address the use cases where a good or bad RIM bundle is sent with an initial provision and then replaced by the other. This grew beyond the scope of this PR and will be handled in a future issue.
Closes #808