Fix possible collisions when attribute is renamed

[lmolkova]

See open-telemetry/semantic-conventions#1031 for the details

TL;DR:

to_const_name jinja helper generates the same constant name for foo.bar and foo_bar.
Tooling will provide a better helper, the workaround for now is to use custom macro

e.g.

{%- macro to_const_name_v2(attribute_name) -%}
{{attribute_name | replace("_", "__") | to_const_name}}
{%- endmacro %}

So that no collision would happen.

We're still collecting input on how a good format would look like

[jack-berg]

Based on this comment I believe this is resolved:

How to resolve client.id vs client_id - open-telemetry/semantic-conventions#1031 (comment) - manually drop messaging.client_id.
Existing jinja and build-tools solution implements it already and here's the weaver-based approach in python
declare a list of excluded ones
exclude them in jinja or in JQ (in python we decided to generate them as comments for transparency)