kubemacpool.io/transaction-timestamp not being populated for new vm created.

It would only work as expected if we apply the vm spec a 2nd time.
This happens for all cases, all vms.

100%

1. following kubemacpool doc (https://github.com/k8snetworkplumbingwg/kubemacpool/blob/main/doc/deployment-on-arbitrary-cluster.md) to deploy kubemacpool: 

```
wget https://raw.githubusercontent.com/k8snetworkplumbingwg/kubemacpool/master/config/release/kubemacpool.yaml mac_oui=02:`openssl rand -hex 1`:`openssl rand -hex 1`
sed -i "s/02:00:00:00:00:00/$mac_oui:00:00:00/" kubemacpool.yaml
sed -i "s/02:FF:FF:FF:FF:FF/$mac_oui:FF:FF:FF/" kubemacpool.yaml
kubectl apply -f ./kubemacpool.yaml 
```

2. following kubevirt quickstart guide 2 to deploy the simplest kubevirt yaml for test purpose: 

https://kubevirt.io/labs/kubernetes/lab1
kubectl apply -f https://kubevirt.io/labs/manifests/vm.yaml

'kubemacpoo.io/transaction-timestamp' annotation is not persisted

'kubemacpoo.io/transaction-timestamp' persists.

initially reported U/S https://github.com/k8snetworkplumbingwg/kubemacpool/issues/536