Enhance documentation

[0xFelix]

What this PR does / why we need it:

Enhance documentation by adding resource type / CRD requirements to
README.md and by moving developers documentation to docs/development.md and
expanding it.

Release note:

None

[openshift-ci]

Hi @0xFelix. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[0xFelix]

/cc @lyarwood
/cc @geetikakay
/cc @akrejcir
/cc @dominikholler

[kubevirt-bot]

@0xFelix: GitHub didn't allow me to request PR reviews from the following users: geetikakay, lyarwood.

Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @lyarwood
/cc @geetikakay
/cc @akrejcir
/cc @dominikholler

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lyarwood]

LGTM assuming others are okay with this being in the main README as opposed to a separate contributor or devel doc somewhere?

[kubevirt-bot]

@lyarwood: changing LGTM is restricted to collaborators

In response to this:

LGTM assuming others are okay with this being in the main README as opposed to a separate contributor or devel doc somewhere?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[akrejcir]

@0xFelix Can you please move info for developers to a separate file? It was ok to keep it in README.md when it was small, but now there is a lot of developer info.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[0xFelix]

@akrejcir Done as requested

[akrejcir]

Thanks.

/lgtm
/approve
/ok-to-test

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akrejcir

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 [akrejcir]

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

[akrejcir]

/override ci/prow/e2e-functests
/override ci/prow/e2e-single-node-functests
/override ci/prow/e2e-upgrade-functests

[kubevirt-bot]

@akrejcir: Overrode contexts on behalf of akrejcir: ci/prow/e2e-functests, ci/prow/e2e-single-node-functests, ci/prow/e2e-upgrade-functests

In response to this:

/override ci/prow/e2e-functests
/override ci/prow/e2e-single-node-functests
/override ci/prow/e2e-upgrade-functests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.