Measure time to update statuses of resources in reconfig tests

[pleshakov]

Include measuring time it takes for NGF to update statuses of resources during a reconfiguration.

There are two main outputs of the NGF:

• updated NGINX configuration with NGINX being reloaded (we check for that in reconfig test)
• updated statuses (we don't)

Statuses tell users (CI/CD pipelines or humans) that resources have been successfully processed and applied, which is a trigger for them to take actions - for example, roll back in case of problems or proceed further in their steps in case of success.

Additionally, NGF cannot process any resource changes while it is update statuses, so if we have bugs there, they affect how quickly NGF responds to changes in a cluster.

Also note that if NGF leader (which updates statuses) processes cluster changes at much different speed than NFG follower, that could lead to configuration skews among NGF replicas.

Considering that, it is important to measure status updates.

Acceptance criteria:

• In addition to measuring reload time, measure time it takes for NGF to update statuses of resources during a reconfiguration.
• The reconfiguration tests are ran again and the results updated for 1.0

[kate-osborn]

Blocked by #1131