Freeze large resources upon deletion request

[paynejd]

Deleting a large repo or org is pretty confusing for a user. There is no "Processing" flag. Content is not "frozen". They can continue to interact with the content while it is being processed asynchronously without any indication that it is being deleted.

Ideas for how we handle this:

• Implement "Frozen" flag -- content that is frozen can only be viewed; the flag should be visible to users
• When requesting a delete, OCL first "freezes" the content (assuming that this is a quick process?), and then kick off the deletion process

The idea is that "Freezing" content will be useful for other purposes: Loading a large repo; processing a large version; evaluating a large expansion; etc.

Finally, if I request a delete in TBv3, the UI should immediately respond, display a flag, etc.

[jamlung-ri]

Thanks @paynejd , this feels valuable for v3 for sure. Currently, I imagine that it's not super common to do large deletes right now, so I could imagine this development waiting for the v3 CodeSystem Author persona work. That said, if this is a low effort change, then I do think it's possible to put it into OCLv2 since the Frozen flag seems pretty simple from a UI perspective. I'll defer to you and @snyaggarwal though.