Clean up the submission/delivery code

[mkalish]

User Story

As a RS developer, I would like the delivery submission endpoints to work effectively and to be well tested

Description/Use Case

The code for these endpoints is brittle and does not support easily iterating on the pipeline. Since the report lineage is agnostic of the steps the code should be able to be refactored to not need to specifically pull date out of the specifically named steps.

Risks/Impacts/Considerations

• The endpoints no longer working as expected; however the understanding is that they are rarely used so the risk is low

Dev Notes

• The recursive query can likely be replaced in favor the new report graph code

The problem code is below. The issue is that the route steps are hardcoded rather than being flexible to support arbitrary steps

descendants.filter { it.actionName == TaskAction.translate }.forEach { descendant ->
                enrichWithTranslateAction(descendant)
            }
            descendants.filter { it.actionName == TaskAction.route }.forEach { descendant ->
                enrichWithRouteAction(descendant)
            }
            descendants.filter { it.actionName == TaskAction.convert }.forEach { descendant ->
                enrichWithConvertAction(descendant)
            }

Acceptance Criteria

• The delivery/submission endpoints are flexible enough to support any adjustments to the UP steps without having to be amended
• Database tests are written to cover the functionality

[Andrey-Glazkv]

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @jack-h-wang @jalbinson @mkalish @thetaurean

[Andrey-Glazkv]

Please add your planning poker estimate with Zenhub @JFisk42

[Andrey-Glazkv]

Please add your planning poker estimate with Zenhub @david-navapbc