Consider changing property naming convention

[trask]

The Java instrumentation repo is using - instead of _ in property names, e.g. otel.java.disabled.resource-providers instead of otel.java.disabled.resource_providers.

Copying comment here from open-telemetry/opentelemetry-java-instrumentation#1414 (comment) in favor of kebab-case:

Spring Boot env var / system property mappings supports both camelCase and kebab-case, but recommends kebab-case:

Property	Note
acme.my-project.person.first-name	Kebab case, which is recommended for use in .properties and .yml files.

And also interestingly:

The prefix value for the annotation must be in kebab case (lowercase and separated by -, such as acme.my-project.person).

[bogdandrutu]

@jkwatson I think this needs to happen before 1.0 if we want to do it

[jkwatson]

this is all in the auto-instrumentation module, which is still tagged as -alpha so we can still address it after 1.0.0, I believe. Also... do we actually have anything with dashes or underscores at all right now? My quick search didn't uncover any.

[jkwatson]

oh...the only one I found was "otel.java.disabled.resource_providers" (and, yes, obviously this was what was being talked about).

[jkwatson]

And, this isn't in the autoconfigure module. 🤦 sorry for the brain fart.

[jkwatson]

I don't have much of an opinion on this one at all. Consistency with auto-instrumentation is probably the most important thing.

[jkwatson]

does the otel spec have any opinion (even implicit) in the naming of things like this?