Remove misleading logs about connecting to agent when running with --force-config

[ppalucki]

Describe the bug
when run like this:

./cri-resmgr --force-config config.yaml 

with no intetion of using cri-regmgr-agent

I'm getting such warnings in output:

W1116 15:10:52.288077  680245 log/ratelimit.go:97] <rate-limited> [core]grpc: addrConn.createTransport failed to connect to {/var/run/cri-resmgr/cri-resmgr-agent.sock /var/run/cri-resmgr/cri-resmgr-agent.sock <nil
> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/run/cri-resmgr/cri-resmgr-agent.sock: connect: no such file or directory". Reconnecting...

Expected behavior
With --force-config when I don't want to use agent, there should be no errors like this.

To Reproduce
just run ./cri-resmgr with --force-config but without agent