chore: rename registry to provider

[dyladan]

Fixes #740

Because of the spec changing the name they use, we need to use the "provider" naming scheme. This is a simple rename and changes no behavior.

[codecov-io]

Codecov Report

Merging #699 into master will increase coverage by 1.72%.
The diff coverage is 94.52%.

@@            Coverage Diff             @@
##           master     #699      +/-   ##
==========================================
+ Coverage   89.69%   91.42%   +1.72%     
==========================================
  Files         214      214              
  Lines       10045     9946      -99     
  Branches      931      913      -18     
==========================================
+ Hits         9010     9093      +83     
+ Misses       1035      853     -182

Impacted Files	Coverage Δ
...entelemetry-exporter-zipkin/test/transform.test.ts	100% <ø> (ø)	⬆️
...ackages/opentelemetry-web/src/WebTracerProvider.ts	100% <ø> (ø)
packages/opentelemetry-tracing/test/Span.test.ts	100% <ø> (ø)	⬆️
packages/opentelemetry-web/test/WebTracer.test.ts	0% <0%> (ø)	⬆️
...metry-core/src/trace/instrumentation/BasePlugin.ts	86.84% <100%> (ø)	⬆️
...lugin-https/test/functionals/https-package.test.ts	98.48% <100%> (ø)	⬆️
...ry-plugin-dns/test/functionals/dns-disable.test.ts	100% <100%> (ø)	⬆️
...ry-tracing/test/export/SimpleSpanProcessor.test.ts	100% <100%> (ø)	⬆️
...s/opentelemetry-tracing/src/BasicTracerProvider.ts	100% <100%> (ø)
...telemetry-node/src/instrumentation/PluginLoader.ts	92.72% <100%> (ø)	⬆️
... and 74 more

[bogdandrutu]

Provider is not a good name for languages that support DI. Can you show me in the specs where that is suggested?

[dyladan]

@bogdandrutu the current spec is "Factory" but there is a vocal minority group that doesn't like that. I suggested "Registry" and @yurishkuro didn't like that because you don't actually register tracers with it, it provides tracers. The current suggestion that seems to be acceptable by most people is "Provider" and I am currently using that language in my PRs to the spec.

Honestly, I would rather call it Factory since it is a factory pattern. I don't know why such a simple thing can be blocking named tracers for so long.

We need to decide on a name so that we can release the next version. We don't want to release with "Registry" just to be told by spec that we need to change to something else. Because we haven't released with named tracers yet, now is a good time to make this change.

[dyladan]

Based on a simple survey of other sigs it looks like one name has no real agreement:

• Java - Factory
• Python - tracer_source
• Go - Provider

From @yurishkuro: https://github.com/open-telemetry/opentelemetry-specification/pull/408/files#r366501814

open-telemetry/oteps#76 converged on Provider rather than Factory.

Here is the original conversation on otep 76 open-telemetry/oteps#76 (comment)

[dyladan]

Closed in favor of #749