Resolve all asset types being evaluated during upload validation

[aaronkanzer]

Moving PR #1818 (Cc @kabilar) to here so there is access to env vars in CI

Also 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

[waxlamp]

I think we need a bit more explanation of the actual bug, and why this fixes it. We need to be careful with Zarr statuses because those have a complex relationship with Assets that results in (perhaps overly) complex semantics.

[waxlamp]

What was the problem that led to this particular change? We need @jjnesbitt to confirm, but I don't think we should be counting Zarr archives in the UPLOADED state (those have not yet been "finalized" in the terminology of the Zarr API; once they are, I believe they move into the COMPLETE state).

[aaronkanzer]

Good catch -- updated to COMPLETE here and in the unit test.

The expansion of the filter query here is to match similar logic in the validate_pending_asset_metadata Celery task -- specific code reference here

[aaronkanzer]

I think we need a bit more explanation of the actual bug, and why this fixes it. We need to be careful with Zarr statuses because those have a complex relationship with Assets that results in (perhaps overly) complex semantics.

In the case where there is no blob but just zarr FKs associated with the Asset, validation fails since the query of:

'numberOfBytes': 1 if version.assets.filter(blob__size__gt=0).exists() else 0,

only evaluates the blob Foreign Key. I stumbled upon this bug when uploading a dandiset of pure zarr if you'd like to replicate in DANDI Archive + dandischema's current state