Upload unification & upgrades

[gsfr]

Edited by @kofalt - itemized list:

1. Lay initial groundwork for upload unification. (@kofalt)
2. EnginePlacer is written but needs to be rigged up and connected to the endpoint. (@nagem)
3. LabelPlacer and (new) UidPlacer should replace most logic currently in upload.reaper and upload.uploader. (@rentzso)
4. After that is complete, consider unifying the LabelPlacer & UidPlacer. (@gsfr)
5. Generate closures for on-the-fly processing; performance optimization. (@kofalt)
6. Once all the above is complete, consider input schema unification(@gsfr)
7. Once all the above is complete, consider Placer naming changes (@kofalt)

[kofalt]

It's my understanding that the UIDPlacer and LabelPlacer are complete, ticking that box. The code basically is unified right now via subclassing, so ticking that box. We punted on closure generation, and naming turned out to be fine, so ticking those boxes. Editing final placer box to be unassigned. Moving ticket back to @gsfr for prioritization of the last items :)

[gsfr]

Let's talk about schema unification at standup tomorrow. I'd also love to finally get rid of the schema composition loopback shenanigans.

[nagem]

While working on #360, I noticed that upload.reaper is still there. Has the reaper been updated to use either the label or UID endpoint, and if so, can this be removed? @gsfr @rentzso

[gsfr]

Yes, we only use /upload/uid and /upload/label.

[kofalt]

Can we close this given that @nagem is working on jinja stuff, which will probably handle dedup?

[gsfr]

Let's reserve @nagem the gratification of closing this from her anticipated jinja PR.

[nagem]

How do we feel about "input schema unification" after #406?

[gsfr]

Keeping this open per offline discussion with @nagem.

[nagem]

Input schema has been considered, keeping separate is the best option available.