ULIMS Integration for Visit Directories

Part of https://github.com/DiamondLightSource/sm-bluesky/issues/373 Backend Integration/ Experiment Manifest / Post Collection Tagging/ Pocessed Data

Automatically resolve and propagate the active visit directory via ULIMS, removing the need for manual text-field input on each screen

### Goals

Acceptance criteria : What journeys should the user be able to complete to consider your feature done
Be as specific as you can, check them off once they work. Add more if you find more requirements during development. Issue should only be considered done after all of them are checked

- [ ] Zero-Manual Visit Input: The active visit directory resolves automatically behind the scenes and maps data storage paths without user configuration.

### Tasks

base on the goals, deduce the tasks required. check them off once they're done
> [!Caution]
> ULIMS API Client? We need to get the information form ULIMS.
> - [ ] Dynamic Directory Hook: Resolve active visit details and propagate them to the active file writer and workflow.

Start by locating the ULIMS API client requirement, then trace how the active file writer and workflow currently receive visit details. Define the integration needed to resolve the active visit directory and map storage paths without user configuration. Done means the zero-manual visit input journey works end to end.

Written by the indexing model from the issue text.