Proof-of-concept port of ApplicationAbleFlight using annotations

[pshapiro4broad]

This POC shows how using StepInput and StepOutput annotations could simplify stairway flight and steps.

If you're not familiar with this code, compare these versions with the code in ApplicationAbleDaoStep, ApplicationAbleIamStep, etc.

These annotations support a form of static data flow analysis. I added a test that generates this output to show what information the annotations provide. Note that without running a step you can't tell which outputs are actually written to by the code, so this prints out all outputs as being potential step outputs.

Test output:

StepData[stepName=ApplicationAblePrecheckStepV3, inputs=[authUserInfo, workspaceId, applicationAbleEnum], outputs=[wsmApplication, applicationAbleDao, applicationAbleSam, response, statusCode]]
StepData[stepName=ApplicationAbleIamStepV3, inputs=[authUserInfo, workspaceId, applicationAbleEnum, wsmApplication, applicationAbleSam], outputs=[response, statusCode]]
StepData[stepName=ApplicationAbleDaoStepV3, inputs=[workspaceId, applicationAbleEnum, applicationAbleDao], outputs=[response, statusCode]]

[pshapiro4broad]

By default, the inputs and outputs are mapped to flight map (or flight input map) elements by using the annotated field's name. You can also provide an annotation argument to use a different name instead.