Remove content from pages which have been moved

[trask]

to avoid mistakes like this #3663 (comment)

[trask]

Looks like there's a lot of references from the spec to the semconv pages, is it ok to just update these to point to the semconv repo? or is the spec repo supposed to avoid links to semconv repo?

bookmark-not-found ./specification/performance-benchmark.md(20,3): Cannot find bookmark '#service' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/compatibility/prometheus_and_openmetrics.md(399,1): Cannot find bookmark '#service' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/resource/sdk.md(34,1): Cannot find bookmark '#semantic-attributes-with-sdk-provided-default-value' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/configuration/sdk-environment-variables.md(80,146): Cannot find bookmark '#semantic-attributes-with-sdk-provided-default-value' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/configuration/sdk-environment-variables.md(81,52): Cannot find bookmark '#service' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/compatibility/opentracing.md(139,1): Cannot find bookmark '#opentracing' in 'specification/trace/semantic_conventions/compatibility.md'.
bookmark-not-found ./specification/protocol/exporter.md(175,162): Cannot find bookmark '#telemetry-sdk' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/common/attribute-naming.md(68,3): Cannot find bookmark '#pluralization' in 'specification/metrics/semantic_conventions/README.md'.
bookmark-not-found ./specification/logs/data-model.md(463,1): Cannot find bookmark '#attributes' in 'specification/logs/semantic_conventions/exceptions.md'.
bookmark-not-found ./supplementary-guidelines/compatibility/aws.md(41,10): Cannot find bookmark '#sqs-event' in 'specification/trace/semantic_conventions/instrumentation/aws-lambda.md'.
bookmark-not-found ./specification/trace/sdk_exporters/jaeger.md(60,8): Cannot find bookmark '#service' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./specification/trace/sdk_exporters/zipkin.md(100,17): Cannot find bookmark '#general-remote-service-attributes' in 'specification/trace/semantic_conventions/span-general.md'.
bookmark-not-found ./specification/trace/sdk_exporters/zipkin.md(101,19): Cannot find bookmark '#server-and-client-attributes' in 'specification/trace/semantic_conventions/span-general.md'.
bookmark-not-found ./specification/trace/sdk_exporters/zipkin.md(102,25): Cannot find bookmark '#server-and-client-attributes' in 'specification/trace/semantic_conventions/span-general.md'.
bookmark-not-found ./specification/trace/sdk_exporters/zipkin.md(103,47): Cannot find bookmark '#server-and-client-attributes' in 'specification/trace/semantic_conventions/span-general.md'.
bookmark-not-found ./specification/glossary.md(120,1): Cannot find bookmark '#telemetry-sdk' in 'specification/resource/semantic_conventions/README.md'.
bookmark-not-found ./spec-compliance-matrix.md(244,3): Cannot find bookmark '#semantic-attributes-with-sdk-provided-default-value' in 'specification/resource/semantic_conventions/README.md'.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[carlosalberto]

is it ok to just update these to point to the semconv repo? or is the spec repo supposed to avoid links to semconv repo?

I think that's totally fine (cc @chalin @open-telemetry/specs-semconv-approvers please confirm)

[joaopgrassi]

It seems we missed this one under /common when initially adding the move notice:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/url.md

[chalin]

LGTM

Later we might consider support auto-page redirect as was mentioned earlier, and possibly a change in wording (e.g., "This page has moved to ...").

[carlosalberto]

@trask So yes, we can point to the spec repo directly. Once that is done, we can merge this PR ;)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.

[trask]

Closing in favor of #3711 (thanks @jsuereth!)