Segy to VDS Postman Collection - Retrieving vds_id from storage record

This MR fixes the issue on step 6 where the VDS id is invalid returning a 404. The issue is that the VDS id is no longer set from the post request to execute the open VDS Dag run. The VDS id is now retrieved from the dataset storage record properties.

Example response from storage where the id is retrieved:

"data": {
        "DatasetProperties": {
            "FileCollectionPath": "sd://osdu/autotest",
            "FileSourceInfos": [
                {
                    "FileSource": "sd://osdu/autotest/ST0202R08_PS_PSDM_RAW_PP_TIME.MIG_RAW.POST_STACK.3D.JS-017534.2ced8891-5bfa-4e3c-ac57-4653ad8639d8.vds"
                }
            ]
        }
    },

vds_id = ST0202R08_PS_PSDM_RAW_PP_TIME.MIG_RAW.POST_STACK.3D.JS-017534.2ced8891-5bfa-4e3c-ac57-4653ad8639d8.vds