chore(resource-detector-azure): use exported strings for attributes

[maryliag]

Which problem is this PR solving?

• Part Of Update usage of semantic conventions to new exported strings #2025

Short description of the changes

On package opentelemetry-resource-detector-azure:

• Update @opentelemetry/semantic-conventions from ^1.0.0 to ^1.22.0
• Use exported strings for Semantic Resource Attributes, Cloud Platform Values and Cloud Provider Values.

[JamieDanielson]

Just a note, I recently updated the CONTRIBUTING doc because we no longer need to update the changelog on our own in PRs - it gets updated in the releasing step!

[codecov]

Codecov Report

Merging #2048 (f4fa499) into main (dfb2dff) will decrease coverage by 0.34%.
Report is 36 commits behind head on main.
The diff coverage is n/a.

❗ Current head f4fa499 differs from pull request most recent head cd268b2. Consider uploading reports for the commit cd268b2 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2048      +/-   ##
==========================================
- Coverage   90.97%   90.63%   -0.34%     
==========================================
  Files         146      146              
  Lines        7492     7488       -4     
  Branches     1502     1494       -8     
==========================================
- Hits         6816     6787      -29     
- Misses        676      701      +25     

Files	Coverage Δ
...tor-azure/src/detectors/AzureAppServiceDetector.ts	96.66% <ø> (ø)
...ctor-azure/src/detectors/AzureFunctionsDetector.ts	100.00% <ø> (ø)
...ce-detector-azure/src/detectors/AzureVmDetector.ts	80.64% <ø> (ø)

... and 8 files with indirect coverage changes

[JamieDanielson]

Looks like the lint step failed. You can ignore the warnings but locally try running npm run lint:fix and that should sort out the errors!

[maryliag]

Updated to remove the changes on changelog.
I was having some issues making my lint run locally, after a few more tries and changes of versions (looks like my Node was too new), I was able to make it work now and fixed the changes 😄

[JamieDanielson]

Thanks for this!

[maryliag]

@JamieDanielson thank you for the review! I don't have permission to merge it, so hopefully someone else can merge it for me 😄

[trentm]

I was having some issues making my lint run locally, after a few more tries and changes of versions (looks like my Node was too new)

🤨 Really? This was 2w ago, so you may not have details. If you do, I'm a little curious if there is an issue with a very new Node.js version.

[trentm]

If you do, I'm a little curious if there is an issue with a very new Node.js version.

FWIW, I was able to lint with Node v21.7.2:

nvm install v21.7.2
npm ci --ignore-scripts
npm run lint

[maryliag]

I don't have the error messages anymore, but if it happens again in the future I will open an issue with details so it can be properly investigated 😄