**Description of the bug** In latest SDK/API, places like https://github.com/open-telemetry/opentelemetry-ruby/blob/b2cac915e2662f91e032097c4e0c6e9395128d64/api/lib/opentelemetry/trace/tracer.rb#L29 incorrectly state it's integer nanoseconds since the epoch when it's really `Time` or `Float` of seconds expected.