feat: add ability to force sync an event into default namespace

[matskiv]

What issue type does this pull request address? (keep at least one, remove the others) /kind enhancement

What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible) resolves ENG-6860

Please provide a short message that should be published in the vcluster release notes Added ability to force sync Events that don't have an involvedObject that is synced from vCluster. These events will be synced into the default namespace.

What else do we need to know?

[cbron]

@matskiv ^

[matskiv]

@hidalgopl to answer your questions:

Just to ensure, this will only work on events from vcluster host namespace, right? Because the syncer watches only events from vcluster host namespace.

Correct. That is an expected limitation.

Were you able to test it? I think we could extend one of the existing e2e tests to annotate existing event and check if it gets synced to the virtual properly.

I did test this by applying a new Event manifest, with the annotation. All the existing events would typically be synced anyway. Should I create a new e2e test that will create a new event and verify it is synced?