TR: Situation related to a Line not affecting the actual `TimedLeg` appearing in in `TripResponseContext`

For connections involving Bern as a Stop (either LegBoard or LegAlight) we always get the PTSituation regarding disruptions between Bern and Olten even though the Trip is not affected (e.g. Fribourg – Bern).

See GIST of current state on INT

Affects doesn't allow us to ignore the PTSituation, as Bern (8507000) is listed as affected.

<siri:Affects>
  <siri:StopPoints>
    <siri:AffectedStopPoint>
      <siri:StopPointRef>8500218</siri:StopPointRef>
    </siri:AffectedStopPoint>
    <siri:AffectedStopPoint>
      <siri:StopPointRef>8507000</siri:StopPointRef>
    </siri:AffectedStopPoint>
  </siri:StopPoints>
  <siri:VehicleJourneys/>
</siri:Affects>

🔎 Whole PtSituation

```xml 2024-09-03T07:44:00Z ski-ddip-out-sx_int ch:1:sstid:100001:88ca2852-406d-498f-9532-79eaee20c4bb-1 3 other 2024-09-02T22:00:00Z 2024-09-04T22:00:00Z unknown unknown 3 stopPoint 8500218 8507000 true 2024-09-03T07:44:00Z Limited train service between Olten and Bern are subject to restrictions. This is due to construction work. Limited train service between Olten and Bern are subject to restrictions. This is due to construction work. The restriction lasts from 03.09.2024, 00:00 until 04.09.2024, 23:59. You have to expect changed timetables. Bikes cannot be transported. Registration recommended for customers in a wheelchair. We recommend you to check your timetable online shortly before travelling. The online timetable will be updated. You have to expect changed timetables. Bikes cannot be transported. Registration recommended for customers in a wheelchair. We recommend you to check your timetable online shortly before travelling. The restriction lasts from 03.09.2024, 00:00 until 04.09.2024, 23:59. ```

openTdataCH / ojp-sdk

TR: Situation related to a Line not affecting the actual `TimedLeg` appearing in in `TripResponseContext` #122