Create a simple object to hold interview steps

[nonprofittechy]

Adds a central filing workflow registry and view context. No template, JavaScript, persistence, or model changes.

This is a very minimalist version of the idea to make it easier to insert or remove steps in the LITeFile workflow. As is, there's no branching logic. A future version could use a state machine. Before a state machine, we should finalize a cleaner way to store interview state than the current randomly stashed keys into three different places.

It's also possible that linear is fine and a state machine isn't needed.

[Copilot]

Pull request overview

Introduces a centralized registry for the e-filing “wizard” steps and a helper to generate consistent per-step navigation context (current/previous/next + URLs), then wires that context into several existing filing views.

Changes:

• Added efile_app/efile/workflow.py with a WorkflowStep registry and helpers for step lookup + prev/next navigation URL generation.
• Updated filing views (options, upload_first, expert_form, payment) to merge the shared workflow context into their template context.
• Removed duplicated login/token logic in options while adding the shared workflow context.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
efile_app/efile/workflow.py	Adds the central workflow step registry and helper functions to compute navigation context/URLs.
efile_app/efile/views/options.py	Injects workflow context into the options step (and cleans up duplicated logic).
efile_app/efile/views/upload_first.py	Injects workflow context into the “upload lead document” step.
efile_app/efile/views/expert_form.py	Injects workflow context into the “case information” step.
efile_app/efile/views/payment.py	Injects workflow context into the payment step.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[BryceStevenWilley]

As is I think this is a great start. I don't think we'd need to go all the way to state machine, but we might want conditional pages at some point? This def supports this with the current API though, so that's fine.