Version bump to 4.11.4

Version bump to 4.11.3

WT-13187: Ensure that initial scripts are properly closed

When serving the main page, either set up through the hybrid or
conventional boot, the script will run, ensuring a response it sent to
the server. This will contain all correct initial start-up information,
and the way the follow-up requests ought to be handled.

In this logic, we also append all initially defined resources for the
application, like stylesheets or JavaScript. The latter is loaded via
WApplication::require. Any script added here was not properly closed.
While the script was still properly loaded, the actual bootstrapping
mechanism that was below it would be commented out, and not be
interpreted by the browser. This results in every new request coming in
to actually be considered a NEW request, and not part of the same
application.

Version bump to 4.11.1

WT-12461: Correctly use WAsioWrapper

Implementations that use a standalone asio (like the Windows builder for
releases) require the use of WAsioWrapper, instead of calling
boost::asio.

Version bump to 4.10.4

Target a specific VS build tools channel

The channel we used before was "Current", meaning any update to it, was
also used locally. This caused an issue where the build tools
misbehaved, and were not able to identify the compiler.

WT-12006: More robustly place the JS member functions

When placing a JS member on a widget, its name and value are remembered.
This is so that if the value is cleared or replaced, we do so for the
same member function.

There, however, exists a special case for member function where if a
single character is assigned to it, it is replaced by an empty value.
This serves to function such that setting the function to `0` for
example, will result in it being empty.

When we appended the semicolon to it, this caused that last piece of
logic to be ignored, and would generate incorrect JS, which called a
function `0;`.

Version bump to 4.10.1

Finalize release notes