[chore] remove microsoft link to fix PR checks

[trisch-me]

Changes

Update link which now redirects to another url and causes markdown-link-check error

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[trisch-me]

Hm it is still not working. @arminru do you know are there special settings for markdown check? I was thinking the problem is in redirecting but final working url is also causing check to fail

[arminru]

@trisch-me Sometimes the link check is a bit spotty, maybe the resolution and/or response is taking too long from the data center where the Github workflow is running. I'd not be surprised if re-running it once or twice would make it pass.
The settings don't override anything w.r.t. redirection: https://github.com/open-telemetry/semantic-conventions/blob/main/.markdown_link_check_config.json
In https://github.com/open-telemetry/opentelemetry.io they improved stability by introducing a cache for external reference checking but we haven't invested in setting this up in this repo here since it used to be working well enough for the most part.

[trisch-me]

@arminru I thought so too, but it looks like it is failing for all PRs.
From config I see we take only "aliveStatusCodes": [200, 403]. The url returns 302 and redirects to another one. But I am not sure it is the issue here because current PR has new url.

Taking into account that it is always failing after 3 minutes it looks like there is some problem with tool itself and it raises timeout

[trisch-me]

Ok it is working now so the problem was with that particular url. But I'm not sure I see the reason why it was failing

[trask]

Ok it is working now so the problem was with that particular url. But I'm not sure I see the reason why it was failing

we've seen issues in the java instrumentation repo with several sites rejecting bot requests: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/0a5c31193cb331dd47733a172db8d39c9e7016dd/.github/scripts/markdown-link-check-config.json#L7-L26

[trisch-me]

Oh I see, so you mean that microsoft start to block requests from this block. This makes sense