Add API deprecation terminology guidance

[p1930n]

Summary

• add style guide guidance for API change terminology
• distinguish deprecated, no longer served, and removed
• discourage using obsolete for Kubernetes APIs

Issue

Fixes #28690

Validation

• git diff --check

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign reylejano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[p1930n]

Local validation completed successfully:

• Built the deploy preview locally with Hugo v0.133.0 using the same preview settings as Netlify.
• Ran npx -y pagefind --site public after the Hugo build.

Both steps completed successfully locally. The Netlify deploy preview has failed twice after about 9m40s, but the GitHub checks only report Deploy failed and the Netlify build logs are not publicly accessible from my side.

Could someone with Netlify access check the build log or retry the deploy?

[p1930n]

Additional context: this Netlify failure does not appear isolated to this PR. I checked nearby PRs and saw the same external deploy failure pattern on #55680 and #55690: deploy/netlify fails and the Header rules / Pages changed / Redirect rules checks all report Deploy failed, with an empty public Netlify summary.

Other nearby PRs such as #55692 have successful Netlify deploy previews, so the failing cases still need the private Netlify build log to identify the actual failing step.

[pacoxu]

A force push(after rebase the latest main branch) will trigger a retest, which may help.