Combine assets and assets_large in the dfx.json

[bdemann]

It would be great if the developers didn't have to worry about which assets need to go where. Is there a way we could combine these two fields so that developers don't need to care about it. We could just run all assets through the assets_large path, but it's much quicker to put as many as possible in the binary. Is there a way to deterministically breakup which assets get uploaded by which method? So when we are creating the binary we run a function to determine which files go where, grab all those that go in the binary include them there, then when we finish building and deploying the binary we can run the same function but this time focus on the files that need to be uploaded via the assets_large approach and do that to those.

[bdemann]

Closed by #1866