Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(vip): ensure finalizer is added in handleAddVirtualIP

When a VIP is created by user (via kubectl or test), handleAddVirtualIP
is called but it didn't ensure the finalizer was added. The
createOrUpdateVipCR function's else branch only updates labels and
status without adding finalizer.

This caused the flaky test "Test vip subnet status update with finalizer"
to fail because the test's WaitToBeReady only waits for Status.V4ip to be
set, which happens before the finalizer is added.

Changes:
- Call handleAddOrUpdateVipFinalizer at the end of handleAddVirtualIP
  for all VIP types to ensure the finalizer is always present
- Add detailed V(3) level logs for debugging finalizer operations
- Skip unnecessary patch when finalizer is already up to date
- Fix error message typo (ovn eip -> vip)