Add reservationId in version 3.0.4 to preSelections in GET /availability/place-map

[Linus-Turnit]

Since we anyway will create a version 3.0.4, we suggest to add reservationId to the preSelection structure in GET /availability/seat-map

{
  "vehicleAvailability": {
    "vehicle": {
      "coaches": [
        {
          "compartments": [
            {
              "places": [
                {
                  "number": "string",
                  "status": "NONE",
                  "isSelectable": true,
                  "placeProperties": [
                    "string"
                  ],
                  "selectionFee": {
                    "currency": "string",
                    "amount": 0,
                    "scale": 0
                  }
                }
              ],
              "number": "string",
              "isSelectable": true,
              "status": "NONE",
              "travelClass": "string",
              "serviceClass": "string",
              "compartmentProperties": [
                "string"
              ]
            }
          ],
          "number": "string",
          "status": "NONE",
          "layoutId": "string",
          "layoutIdUpperDeck": "string",
          "layoutIdLowerDeck": "string",
          "direction": "UNSPECIFIED",
          "owner": "string",
          "specialCoach": "string"
        }
      ]
    },
    "preSelections": [
      {
        "coach": "string",
        "place": "string",
        "reservationId": "string"   <=== This is new
      }
    ]
  }
}

Reason for this is to have the possibility to know where each member in a travel party is seated. This possibility will be handled in version 3.2 of OSDM with a new endpoint POST /availabilities/place-map replacing this end-point.

[schlpbch]

Proposal is to back port the reservationId from version 3.2.