Rewrite the ClusterInterceptors page for clarity and flow

[tualeron]

Changes

Rewrites the ClusterInterceptors page for clarity and flow.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

NONE

[tualeron]

/kind documentation

[tualeron]

/assign @dibyom

[tualeron]

I created issues to keep track of the extra info we need to add to this doc in separate PRs. Since this is just an editorial rewrite, can we get LGTM + approval?

[jmcshane]

/lgtm

[tualeron]

Thanks James. Can we get approval?

[jmcshane]

@sergetron I'm not an owner, so I can't approve PRs. That would have to be @dibyom

[tualeron]

@sergetron I'm not an owner, so I can't approve PRs. That would have to be @dibyom

I know. The approval request was directed at others assigned to the PR.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dibyom]

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