Use datapath with UDA when fetching IDS properties

[maarten-ic]

We request ids_properties/homogeneous_time and
ids_properties/version_put/data_dictionary in two separate calls to the backend before actually getting all data. This is fine for local backends, but UDA would fetch the data three times:

1. When determining the DD version and if the IDS exists
2. When determining whether the IDS uses homogeneous time
3. When actually reading the data

This commit adds a datapath="ids_properties" to the first two cases. This results in UDA only fetching the IDS properties in points 1 and 2. The full IDS is now requested once by UDA, in point 3.

[DaanVanVugt]

if using this argument with AL4 is there a reasonable behaviour? Or should we 'protect' our users from that by checking versions?

[maarten-ic]

if using this argument with AL4 is there a reasonable behaviour? Or should we 'protect' our users from that by checking versions?

We only supply this argument when using the UDA backend, which is not relevant to AL4 IIRC.
This is internal API and not directly called by end users.

[maarten-ic]

Actually, I think at this point it's impossible to use IMAS-Python with AL4: with AL4, there is no imas_core module, and importing the legacy imas module is impossible (since that's the module name of this module).

I'll create a ticket to remove legacy AL4 support from the code

[olivhoenen]

I agree that we do not need to have compatibility with the AL4 lowlevel API (cleaning can be done in a forthcoming PR before the next release).