Integrate dynamic form engine into report screen

Model the report screen as a BlocProvider + BlocBuilder tree at the top level; pass the orchestrator BLoC down rather than recreating it per widget. The DynamicFieldRenderer should be a stateless widget receiving a list of FieldSchema objects and a callback for value changes — it must not own any state itself. Use a sealed class or freezed union for form field types (TextField, CheckboxField, DropdownField, DateField) to ensure exhaustive handling in the renderer. The WayForwardSectionWidget should always be appended after the dynamic fields list, never inside the dynamic list, so it cannot be accidentally omitted by a schema with no fields.

For draft detection, check the orchestrator BLoC state on initState — if hasDraft is true, dispatch a RestoreDraftEvent before building the form. Avoid Navigator.pop inside form submit logic; instead emit a navigation event from the BLoC and handle it in a BlocListener to keep navigation out of business logic.

Widget tests (flutter_test): render loading skeleton when BLoC is in loading state; render dynamic fields matching a mock schema of 5 fields; render way-forward section in all states; render error widget with retry button on schema fetch failure; render empty-schema state when schema has zero fields; pre-populate fields from draft state. BLoC unit tests: emits loading → loaded(schema) on successful fetch; emits loading → error on fetch failure; field update events mutate correct field in state; submit event validates required fields and emits validationError or submitting states. Golden tests for all four screen states. Integration test: full schema fetch from Supabase test instance returns correct fields for test organization.