Change convention for encoding version into package name

Currently we only encode the version into the package name when there is more than one version, e.g.

• io.opentelemetry.auto.instrumentation.apachehttpclient.v2_0
• io.opentelemetry.auto.instrumentation.apachehttpclient.v4_0

but we don't encode the version if there is only one version, e.g.

• io.opentelemetry.auto.instrumentation.apachehttpasyncclient

The idea was that the package names weren't public, so we could change them later if/when we needed a second version.

With the introduction of library instrumentation now, these package names are public, so i think makes sense to change our convention and always encode the version into the package name (for both library and auto instrumentation package names, to keep them similar).

EDIT: this way, if we need to support a new version later, we don't have to add the version to the old package name at that time.

The issue names package conventions for Apache HTTP client instrumentation but does not identify files or tests. Start by locating the library and auto-instrumentation package declarations, then inventory versions that currently omit or include suffixes. Done means both library and auto-instrumentation package names consistently encode their supported version without breaking the stated convention.