Generate semconv constants update for OTel Spec 1.5.0

[NathanielRN]

Description

Updates the semantic conventions constants to the v1.5.0 tag using the ./scripts/semconv/generate.sh script.

Additionally, after learning how to run the script by updating the Docker image tag with @lonewolf3739 's help from this Slack message, I thought it would be helpful to pull that tag version out as a variable in the generate.sh script.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

I manually checked all the variables which changed and ensured that no one in contrib or core was using them. Other than that no tests are needed.

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR: Bump core repo SHA reference to get latest Semantic Conventions opentelemetry-python-contrib#587 (POST MERGE EDIT: In retrospect even though it doesn't BREAK Contrib, we should probably move the Contrib forward at the same time.)

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
  - [ ] Unit tests have been added
  - [ ] Documentation has been updated (Not needed?)

[aabmass]

Can we update the template to reflow long text? https://jinja.palletsprojects.com/en/2.11.x/templates/#wordwrap

[NathanielRN]

Looks like if I update generate.sh like this:

-    {{attribute.brief | to_doc_brief}}.
+    {{attribute.brief | to_doc_brief | wordwrap}}.

it doesn't do the tabs properly 😕

    DEVICE_ID = "device.id"
    """
    A unique identifier representing the device.
    Note: The device identifier MUST only be defined using the values outlined below.
This value is not an advertising identifier and MUST NOT be used as such. On
iOS (Swift or Objective-C), this value MUST be equal to the [vendor identifier]
(https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierfor
vendor). On Android (Java or Kotlin), this value MUST be equal to the Firebase
Installation ID or a globally unique UUID which is persisted across sessions in
your application. More information can be found
[here](https://developer.android.com/training/articles/user-data-ids) on best
practices and exact implementation details. Caution should be taken when
storing personal data or anything which can identify a user. GDPR and data
protection laws may apply, ensure you do your own due diligence.
    """