🌱 Remove challenger traces from here

The challenger has no business logic in here, and kcrypt should just
read what it needs. This goes in parallel with https://github.com/kairos-io/kcrypt-challenger/pull/10
Not blocking each other.

Signed-off-by: mudler <mudler@c3os.io>

pkg/config/config.go

@@ -25,7 +25,6 @@ var MappingsFile = "/oem/91-kcrypt-mappings.yaml"
 
 type Config struct {
 	Kcrypt struct {
-		Server            string            `yaml:"challenger_server,omitempty"`
 		UUIDLabelMappings map[string]string `yaml:"uuid_label_mappings,omitempty"`
 	}
 }