Lock Finalization Cleanup

[nisdas]

What type of PR is this?

Bug Fix

What does this PR do? Why is it needed?

The go runtime makes no guarantees that the finalizer function will be executed after the execution of the last method.
https://pkg.go.dev/runtime#SetFinalizer

However, there is no guarantee that KeepAlive(x) or any other use of x “synchronizes before” f(x), so in general a finalizer should use a mutex or other synchronization mechanism if it needs to access mutable state in x. For example, consider a finalizer that inspects a mutable field in x that is modified from time to time in the main program before x becomes unreachable and the finalizer is invoked.

This would require that in the event we are running our state cleanup, we lock the state when deleting fields to prevent data races and potential panics for this particular case.

Which issues(s) does this PR fix?

N.A

Other notes for review