Basic unit testing coverage for neonvm-controller

[sharnoff]

Optional for neondatabase/company_projects#187.

Problem description / Motivation

The neonvm-controller's reconcile functions are huge and complex, with the majority of testing coming from system-wide end-to-end tests.

This leaves us over-exposed to uncommon scenarios or edge cases, along with little testing against degradations.

Feature idea(s) / DoD

More testing for the reconcile functions, mostly just to get it started. This is a continuing process

Implementation ideas

We may want to do something like what pkg/agent/core/state.go does, where the core of the logic is pure, and just returns the desired action to take.

While that would be a lot of work, maybe it's worth it to "force" all of the state to exist outside the control flow.

Also to look at how other k8s controllers are tested.

Related issues

• move neonvm controller qmp logic into separate package #716
• Neonvm controller codebase improvements #733

Tasks

Preview Give feedback

1. neonvm-controller: introduce unit tests #935
   +0
2. neonvm-controller: expand the tests with QMP mocked #943
   +0
3. Another PR with more thorough coverage and refactoring
4. Show coverage in CI

[sharnoff]

Status:

• neonvm-controller: introduce unit tests #935 waiting on review from @sharnoff, and waiting on switching to standard k8s mock
• neonvm-controller: expand the tests with QMP mocked #943 waiting on previous PR to be finished