[ENG-6945] Added draft registrations page in admin app

[ihorsokhanexoft]

Purpose

User should be able to view users' draft registrations by their guid by the requirement:

Clicking on a draft registration will show the metadata of that draft

Changes

Search by user's guid:

List of his draft registrations:

Specific draft registration page:

Notes

1. Worth to note that DraftRegistrations don't have guid, only _id from ObjectIDMixin, this is why I had to override it in some places
2. Also some templates cannot be reused because DraftRegistration doesn't inherit from Node
3. The following requirement is ignored because admin can click "back" button as the previous page is user's draft registrations

Add a link to the user detail view in the admin app to take the admin to the list of draft registrations associated with that user.

4. In UserDraftRegistrationsList.get_queryset I used draft_registrations_active assuming we don't show deleted drafts

Ticket

https://openscience.atlassian.net/browse/ENG-6945

[brianjgeiger]

One question about a couple of labels, otherwise looks great. Oh, and also Product is wondering if you could put in total storage usage into the detail page.

[brianjgeiger]

Same here with id

[brianjgeiger]

Since draft registrations don't have a guid, would it make more sense to just call this id?

[ihorsokhanexoft]

Yeah, I left it because for Product it's guid and didn't want to confuse them, will rename it

[ihorsokhanexoft]

One question about a couple of labels, otherwise looks great. Oh, and also Product is wondering if you could put in total storage usage into the detail page.

I'll try but this functionality can be reused only if model inherits from Node that is not our case (drafts don't have guid, custom_storage_usage_limit_public, custom_storage_usage_limit_private fields), thus cannot be sure it's possible

[ihorsokhanexoft]

@brianjgeiger I managed to implement it. As expected the issue was that Drafts don't inherit from AbstractNode, but files have relationship to AbstractNode via target_content_type thus added additional conditions