Rename otel.trace.classes.excludes to otel.javaagent.exclude-classes

[trask]

Missed this in #1740.

See latest note about exclude-classes vs excludeClasses: #1414 (comment), though happy to change to something else either in this PR or later on

[iNikem]

I think we should fix our property->env mapping to support excludeAll. This exclude-all is quite unnatural for Java I would say.

[mateuszrzeszutek]

Hmm, we use dash-separated words in the instrumentation names though: e.g. spring-webmvc.
Still, I agree that excludeAll looks more Java-like in this case.

[trask]

I have the same impression about camelCase being more Java-like, but I went looking at the Spring Boot env var / system property mappings, and they support both camelCase and kebab-case, but recommend 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).

So now I'm thinking kebab case is the way to go (and as benefit is consistent with our module names when used in the property names, e.g. otel.instrumentation.external-annotations.exclude-methods).