Empty segment in path error

When listing (`obstore.list`) and object path contains double delimiter exception is thrown.
At least in Azure those paths - while weird - are actually readable. One can even have two different paths like: `container/l1/l2/file.csv`, `container/l1/l2//file.csv`.

As far as I can tell there's no way to ignore the error since the exception would stop the iterator but maybe it could be possible to have a flag that would print warning and ignore such paths? Or if the behaviour was dependent on implementation e.g. if it's not supported in s3 or something it would throw error but if it works in azure it returns those paths?

I know we shouldn't have such a mess with the file paths but unfortunately sometimes it's other people writing for us and we have no influence over that 😅