Resolve all asset types being evaluated during upload validation

[aaronkanzer]

Relates to /linc-archive/pull/34 and #1814

During validation of zarr based datasets, a validation check occurs on the assetSummary field in the dandiset.yaml

Prior to this PR, the only "assets" evaluated were "blob". In the query that is updated in this PR, the checks for size are expanded to not just blob but other "asset" types within the Asset model -- see link below:

dandi-archive/dandiapi/api/models/asset.py

Lines 137 to 145 in 1be249a

	blob = models.ForeignKey(
	AssetBlob, related_name='assets', on_delete=models.CASCADE, null=True, blank=True
	)
	embargoed_blob = models.ForeignKey(
	EmbargoedAssetBlob, related_name='assets', on_delete=models.CASCADE, null=True, blank=True
	)
	zarr = models.ForeignKey(
	'zarr.ZarrArchive', related_name='assets', on_delete=models.CASCADE, null=True, blank=True
	)

Prior to the fix in this PR, the following validation would fail on assets in dandischema such as zarr: https://github.com/dandi/dandi-schema/blob/bdb7dd681435f1092814041eb01eb4fabe87bf57/dandischema/models.py#L1497

[yarikoptic]

if it is a "Draft:" should it better be a "Draft"?

[aaronkanzer]

if it is a "Draft:" should it better be a "Draft"?

@yarikoptic Moved to draft -- going to blame lack of coffee on my side for not making this initially a draft 😄

[aaronkanzer]

Cc @jwodder @yarikoptic @waxlamp -- since I'm submitting via a fork, I don't think that the GitHub Actions pipeline for cli-integration has access to the env vars needed for proper testing with Docker

[yarikoptic]

@aaronkanzer I have added you to the @dandi/dandiarchive team, so you should be able to push a branch to this fork for a PR to gain access to all the secrets. Please resubmit this PR

[aaronkanzer]

Closing to move code to: #2062