Looks ok.

This somewhat weakens our tests, but after talking with the other Python people and also confirmed with Ingest that if there is an onknown value in span data it is just stored anyhow. I think this is fine.

👍 I'm not sure there's a stronger test we can add here as the thread ids are unstable. The only alternative I can think of is to mock it in each place which seems worse because now every test is concerned about mocking the thread id data appropriately to pass. Which is why I opted for each test to just assert that the relevant properties are added to the span data.