Reserve specific taint key prefixes

[sats-23]

Description

1. Reserved taint key prefixes for:

• readiness.k8s.io/system/*
• readiness.k8s.io/core/*
• readiness.k8s.io/node/*
• readiness.k8s.io/device/*
• readiness.k8s.io/network/*
• readiness.k8s.io/storage/*

2. Updated yaml examples and doc to reflect the same

Related Issue

Fixes #3

Type of Change

/kind feature

Testing

Checklist

• make test passes
• make lint passes

Does this PR introduce a user-facing change?

Reserved specific taint key prefixes (readiness.k8s.io/{system,core,node,device,network,storage}/*) for core operations.

Doc #(issue)

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[netlify]

✅ Deploy Preview for node-readiness-controller ready!

Name	Link
🔨 Latest commit	540a938
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/69c0fe508432880008bac1a6
😎 Deploy Preview	https://deploy-preview-177--node-readiness-controller.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sats-23
Once this PR has been reviewed and has the lgtm label, please assign mrunalp 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:

• OWNERS

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

[ajaysundark]

@Priyankasaggu11929 identified in #155 that this is not a valid prefix format for taint (subprefix not allowed in Taints), so this behavior cannot be achieved without upstream change :(