Abstraction on top of Win32 Named Events that can be set only once

[CarlosNihelton]

Abstract

An abstraction on top of Win32 Named Events that can be set only once.

NOTE: Win32 Events (named or unnamed) are resetable, meaning that one can toggle on-off as much as desired. They
can even be automatically reset by the OS, if configured to do so by the CreateEvent function. This class
restricts that behavior by closing the OS handle and nulling out the private field that would represent it, thus
rendering the object useless after being once set.

Usage

Ensure a unique name is used for its initialization. This is an IPC mechanism, so other processes will find it.

SetOnceNamedEvent event(L"unique_identifyier");

When something interesting happens and you want to let the world know about it, set the event:

bool ok = event.set();

That's it. From now on the variable is useless. The event remains valid from a succesfull construction until
it's set.

ASSERT_FALSE(event.isValid())

That will be used to notify the OOBE of the distro registration completion as well as to kindly ask it to quit, events that by nature happens at most once.

[EduardGomezEscandell]

Not usually a purist of noexcepts, but this codebase is quite cool in that they are thoroughly used, so I'd try to keep it that way.

[github-actions]

⚠️ Please check out carefully the isses found by clang-tidy in the new code ⚠️
⚠️ clang-format found formatting issues in the code submitted.:warning:
Make sure to run clang-format and update this pull request.
(1/1)

[CarlosNihelton]

The build workflow is failing due an issue in the flutter action. I'll push another PR to fix the action version temporarily until the upstream is fixed.