Requesting the ability to be able to query/track the status of resource publishing

[mparsons-ce]

@excelsior
As noted in discussion for #929 , it would be useful to be able to track where all processes related to publishing a resource may not have been completed.
The suggestions included:

• adding a property to the envelope for tracking status
• A single property may be fine where steps are sequential, but would a different approach be needed for async activities?

The actions for a consumer may vary depending on what tasks are outstanding.
Based on recent issues, the completion of all tasks that will result in a /resources/ view returning a completed resource is the most important.

[jeannekitchens]

@mparsons-ce please clarify the ask here. Does this need discussion? If so, please meet with Alex.

[mparsons-ce]

@jeannekitchens This request was to address (the fairly rare) scenario where a resource has been published but all of steps necessary to result in a properly/fully populated /resource.
As it is rare, it could be used in trouble shooting:

• if a request for a resource fails, there could be a check to see if the envelope exists and has the equivalent of an "in progress" status
  Not sure what would be returned in this scenario?
• the key is that the CTID is valid for a resource in the registry and needs to be treated different from not found