Output retrieval logic doesn't allow for intermediate progress

Steps like eks require outputs from the persistent step to execute its functionality. The problem is persistent does too much and registers the outputs AFTER all its resources are provisioned. This causes a problem as we can continue with other steps if we have the VPC provisioned for example, but we can't do it in practice because of how we handle outputs. The process of registering outputs should be refactored to be done within the methods instead of the class instead of at the end of the class initialization.

This is related to the work that has been discussed related to splitting persistent into smaller compartmentalized steps (Network, IAM, etc).

Trace the persistent step's initialization and output-registration flow, then inspect how the eks step consumes those outputs. The refactor is complete when outputs become available from the relevant resource methods before the whole persistent step finishes, allowing later steps to proceed with intermediate progress.