Simplify CodeOceanJob, particularly metadata handling

[dyf]

Is your feature request related to a problem? Please describe.
When trying to use CodeOceanJob to handle metadata tags correctly, I spent couple hours looking at the control flow, and I'm still not sure I get it. Some other inconsistencies were also confusing - wrappers around configuration objects in aind-codeocean-api that really were only renaming things. We should also support a reprocessing workflow - registration should be optional.

Describe the solution you'd like
I propose CodeOceanJob be organized as follows:

• Use aind-codeocean-api's request/configuration objects directly for the Register, Run, and Capture steps.
• Add a pass_metadata_to_result flag, default True
• Add a add_data_level_tags flag, default True
• Ensure that all metadata tags are unique (use Set, rather than List)
• Make sure that Run+Capture can be used independently of Register+Run+Capture

[alejoe91]

Hi David,

Thanks for the suggestions. Note that the last point is already in place. You can just skip passing the register_config. In this case the run_capsule_config can specify the data_assets. This is also supported by the trigger capsule.

[dyf]

@alejoe91 what do you think about the other suggestions? I'm happy to take a pass at this.

[alejoe91]

I think they would definitely improve the CodeOceanJob class. If you have time to make a PR I would be happy to review it. Otherwise I can also take a stab at it!