Consider using go module paths for scope name in demos #5412
Description
Problem Statement
I noticed the rolldice example has a single-word name for the meter and tracer:
opentelemetry-go/example/dice/rolldice.go
Lines 12 to 17 in ca93aae
I haven't checked other examples, but IMO we should consider doing this across all of them.
Proposed Solution
Since many users will use this as a starting point for their code, would it make more sense to use a "real" scope name? E.g. go.opentelemetry.io/otel/example/dice
?
Alternatives
Keep simpler names for samples