In most cases we only care about the directly attached actions on flownodes. FlowNode.getAction has been identified as ~25% of runtime for pipeline flow analysis, and it is likely b/c this queries all TransientActionFactories for actions.
1. Add a FlowNode.getAction API version (name TBD) that only iterates through the directly added actions (already cached in-object)
2. Switch the pipeline-graph-analysis plugin and stage view's REST API to use this exclusively
3. Benchmark to see what the performance difference is
UPDATE: Doubles stage view performance, which should carry through to a large extent anywhere we use flow analysis.