Fix README manifest links

That has been replaced with sveltos-manager.

Remove any refence to cluster-api-feature-manager

Registers for ability to change log severity at run time

Use libsveltos

Switch to use libsveltos deployer

Use libsveltos clusterproxy

Get rid of:
- getUnstructured
- getDynamicResourceInterface

Use utils package from libsveltos

Use clusterproxy to check if cluster is ready

When a ClusterProfile is managing an helm chart and stop managing it,
instead of removing the chart, if there is another ClusterProfile
currently queue to manage it, simply pass control

ClusterProfile: helm chart behavior

Update sveltos.png

Fix test

When Cluster stops matching a ClusterProfile, by default:
1. all Helm charts deployed in the Cluster by the ClusterProfile
instance are withdrawn;
2. all Kubernetes resources deployed in the Cluster by the
ClusterProfile instance are withdrawn.

This PR introduce a knob, on ClusterProfile Spec, to make this behavior
configurable.
Setting StopMatchingBehavior to:
1. WithdrawPolicies (default behavior) instructs Sveltos to withdraw
all Helm charts and Kubernetes resource deployed by the ClusterProfile
instance;
2. LeavePolicies instructs Sveltos to leave Helm charts and Kubernetes
resources in the cluster.

Introduce StopMatchingBehavior

Prepare for release v0.2.0