Improve documentation by creating a user guide for recording and installing security profiles based on use cases

[ccojocar]

What would you like to be added:

We should write a user guide for recording and installing security profiles based on use cases. This will improve the user experience when using the security profiles operator to manage security profiles in general.

With the introduction of spoc CLI, spo provides now capabilities to manage security profiles beyond the Kubernetes clusters. We should add a detailed step by step guide for following use cases:

• Manage security profiles in-cluster such as seccomp and apparmor, this is the standard use case to record and install security profiles within a k8s cluster.
• Manage security profiles for containers outside of k8s, step by step guide how to use the spoc CLI in this case
• Manage security profiles on your local Linux system, this is the case when someone wants to record and install a security profile for a process running on a local system, this use case is also now covered by the spoc CLI, and it can provide a seamless experience when Support in spoc CLI for install /remove apparmor profiles into the local system  #2387 is implemented.

Why is this needed:

Improve user experience and facilitate the spo adoption.

User story covered

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ccojocar]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ccojocar]

/remove-lifecycle stale