upload-to-unstable/experimental workflows can't be used for packages going through NEW

Any upload that ends up in NEW (so entirely new packages in unstable, or existing packages that are not yet present in experimental for experimental, or updates that add new binary packages) needs to include at least one binary build (usually amd64), otherwise it's rejected by dak.

We should figure out a way to improve the workflow so that it does the right thing.