feat: add reasons to AirbyteStreamStatusTraceMessage

[subodh1810]

Tech spec
Protocol review doc

Sample JSON

{
    "type": "TRACE",
    "trace": {
        "type": "STREAM_STATUS",
        "emitted_at": 1.714638052064E12,
        "stream_status": {
            "stream_descriptor": {
                "name": "stream-name",
                "namespace": "stream-namespace"
            },
            "status": "INCOMPLETE",
            "reasons": [{
                "type": "RATE_LIMITED",
                "rate_limited": {
                    "quota_reset": 1714638052064
                }
            }]
        }
    }
}

[michel-tricot]

Ship it!

[cgardens]

any reason this isn't just a big int? do we need decimals?

[subodh1810]

@cgardens I am just following the convention. We are using number for timestamp attributes. For instance take a look at the emitted_at in AirbyteTraceMessage, its defined as a number

      emitted_at:
        description: "the time in ms that the message was emitted"
        type: number

[jdpgrailsdev]

@cgardens @subodh1810 This looks like a bug in the AirbyteTraceMessage. It was not obvious to me that integer was not an integer data type and is actually a big integer or that number is a floating point/double. Should we attempt to fix the AirbyteTraceMessage either as part of this PR or in a separate PR?

[cgardens]

• let's do it correctly here and use integer.
• let's create an issue to fix airbyte trace meesage and add a todo in the code that that should have been number. don't think this is a good moment to try to fix this old mistake. just want to do it right going forward.

[subodh1810]

@cgardens @jdpgrailsdev added the TODOs in the protocol yaml and created a github issue
https://github.com/airbytehq/airbyte/issues/38163

[jdpgrailsdev]