Consider Path Signals

[callumforrester]

Some string PVs are intended only to store file paths, e.g. the HDF5 plugin write path. Perhaps there is value in representing these with a Signal[Path] rather than a Signal[str] and performing some validation on input values.

See ophyd_async.epics.areadetector.writers.nd_file_hdf.NDFileHDF for an example.

@coretl any thoughts?

[DominicOram]

👍 from me

[coretl]

Could be done, but I'd say this is low priority compared with the other things we're doing

[callumforrester]

Will leave it as a good first issue then

[coretl]

Closing as PathProvider makes the above usecase less compelling. We can revisit after 1.0 if this is still needed