Optimize dandiset owner PUT endpoint

[mvandenburgh]

Now that django-allauth uses a regular JSONField for SocialAccount.extra_data, we can optimize the dandisets owner PUT endpoint to be more efficient and do less SQL queries. See release notes for allauth here https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#0580-2023-10-26

[jjnesbitt]

LGTM

Changes

[mvandenburgh]

Looking at this again, the original ORM expression I wrote can be simplified - see 5cb05e6. I tested it and it works just as well as the previous query.

[jjnesbitt]

@mvandenburgh I noticed that we're still calling the get_user_or_400 query n many times, which can be avoided. I pushed 28f0dca which does it in one query (two if you include the count check). It also removes the check about the empty owners list, since I'm not even sure how that could be triggered (a 400 would be raised before that in any case).

Let me know what you think. Sorry for the trampling, it wasn't possible to achieve the whole diff with github suggestions.

---

Update I've fixed the tests and linting, sorry about that. All should be good now.

[dandibot]

🚀 PR was released in v0.3.64 🚀