Telemetry Correlation
Hi - 

I see from this issue #352 that there was a suggestion to use [launch dashboard api](https://github.com/shahar603/Launch-Dashboard-API) for first stage telemetry which is a great API - so completely agree data should live with them.

My concern is that there's no easy way for developers to actually reconcile between the two API's. This basic query gives an example of the problem we face

```
curl http://api.launchdashboard.space/v2/launches/spacex/ | jq
```

I am observing miss matching flight numbers which is not ideal because we can't use that as a key. Furthermore, i also observe a missmatch between mission identifiers which means we can't use that as key either.

**Some examples**

NROL-108 flight number 112 vs 117
starlink-11 flight_number 102 vs 105
Saocom-1b flight_number 101 vs 104

[Suggestion that they should match](https://github.com/shahar603/Launch-Dashboard-API/issues/17)

Can i suggest that we look to support their 'launch_library_2_id' key as a new property to the launch schema. Or alternatively, we could utilize the links array and provide a URL to the telemetry data? Ideally, a new field would be best to allow greatest control over what what developers can do with the key. I see this as the best way to ensure consistency across the API's without both repos having to reconcile and fix miss-matches as a going concern.

Also happy to raise this ticket against them, but i fear it will keep happening.

Thanks for your great work.