Decide about sending transaction/span timestamp if the user sets it
https://github.com/elastic/apm-agent-rum-js/blob/cda6c9e4dd8b92f9063de3d9b98d0a819cd9a287/packages/rum-core/src/performance-monitoring/span-base.js#L48
Docs - https://github.com/elastic/apm-agent-rum-js/blob/cda6c9e4dd8b92f9063de3d9b98d0a819cd9a287/docs/transaction-api.asciidoc#transactiontimestamp
@jahtalab what are the use cases for specifying a timestamp in RUM?
OpenTracing API has a timestamp on spans, currently we convert that into relative times for the spans and ignore the timestamp. This is mostly for edge cases where an advanced user knows the consequences of setting a timestamp but still need to set it.
But, again this issue is also for discussing whether we want to allow that or not.