fix(blank): uploader is no longer technically required since arborist…

[Avantol13]

… is used for authz

New Features

Breaking Changes

• indexd blank record endpoints no longer require uploader field

Bug Fixes

Improvements

Dependency updates

Deployment changes

[github-actions]

The style in this PR agrees with black. ✔️

This formatting comment was generated automatically by a script in uc-cdis/wool.

[paulineribeyre]

for future reference

The flow now uses arborist to determine if you can create blank records and I think we should allow people to not specify an uploader since it's technically an optional field on the record.
The frontend still relies on the uploader field being there for the current data upload flow / mapping, and for commons that still use acl instead of authz, we still need uploader to know if the user can update the blank record. The Gen3 client for data upload flow still uses only the acl and does update the uploader.
In other words, I think this is backwards compatible, you can either do data upload the old way, or the new way, you just no longer get an error if you try the old way and don't add an uploader for some reason