Convert UDCDirectoryProvider to standard pattern

[DiamondJoseph]

Instructions to reviewer on how to test:

1. Check Hyperion PR still behaves as expected
2. Convert UDCDirectoryProvider to standard pattern hyperion#1352

Checks for reviewer

• Would the PR title make sense to a scientist on a set of release notes
• If a new device has been added does it follow the standards
• If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly

[olliesilvester]

Couple of nitty comments, but the logic and test looks good!

[olliesilvester]

I think change the name of this class since it should be used specifically for storing panda postition data, something like PandaPcapDirectoryProvider?

Also, this DirectoryProvider points to a panda subdirectory which doesn't exist by default. We should add a comment to warn that this directory must already exist when using with a PandA - I don't think there's logic in the HDF writer or the IOC to create the directory for us

[DiamondJoseph]

Something coming down the pipe on that respects: https://github.com/bluesky/ophyd-async/blob/5c116e293afb54b437ffa2ab380635a3c96b19b2/src/ophyd_async/core/_providers.py#L116 Will be handled in the PandA hdf writer at some point. I'll revisit tomorrow

[olliesilvester]

We need to create the panda directory if it doesn't already exist before we connect to the panda. I'm not sure if this feature should ultimately be within dodal or the HDFPanda device, but we can put it in dodal for now at least. This can be done in a separate PR though

[olliesilvester]

Thanks! I'll add something to create the panda directory if it doesn't already exist, in a separate PR