Thank you for contributing to the Bareos Project!

win-native: changes required to build and test

These changes allow us to build and test Bareos on
windows natively built with the MSVC compiler.

• Some system tests do not work on windows (yet). These are
  in the TESTS_TO_SKIP list so that there is a central point
  to disable them.

• Required dlls will be copied to the run directory of the produced
  binaries to run system and google tests easier without to hassle too
  much with the PATH settings. (See BareosCopyDllsToBinDir)

• The sysemtests were adapted to be able to support both Debug and
  Release build types. The current value is provided in
  the environment variable CMAKE_CONFIG_TYPE

• Wherever cmake creates files, we now set the NEWLINE_STYLE to UNIX.
  This makes sure that the bash shell that is also used on windows
  to run the system tests gets correct line endings.

• CMake can both produce MS Build Projects for VisualStudio (default)
  and "Ninja Multi-Config" Projects. The latter has the advantage that
  it supports ccache.

• To make ccache work, we need CMake >= 3.25 and CMP0141 set to NEW.
  This way we can set(CMAKE_MSVC_DEBUG_INFORMATION_FORMAT Embedded)
  Which removes compiler switch /Zi which is unupported by ccache.

• Most external dependencies are provided via vcpkg.

• To package the resulting windows binaries, an own nsi installer file
  winbareos-native.nsi was created.

• The services used by the systemtests are installed by nssm.
  This is required as it is not possible to start the windows binaries
  detached. Nssm also takes care of stdout and stderr and writes this
  output as logfiles into the systemtests' directory.

• Special start/stop scripts bareos-ctl-* for windows have been added
  which take care of the creation and removeal of nssm services for the
  required binaries.

• The start/stop script bareos in the systemtests has been adapted to
  uniformly support multiple directors/filedaemons/storagedaemons.
  To add an additional services, just create a subdirectory
  in the format bareos- parallel to the bareos directory in
  the tests. The startscript will automatically create services for
  all directors, filedaemons and storage daemons that have a
  configuration below this directory. For examples check
  multiple-clients/etc/bareos-secondclient and
  autoxflate/etc/bareos-sd1

• Some scripts remove unexpected windows line ending characters \r
  so that the bash shell can handle everything as needed.

• All systemtests have been configured to disable VSS in the filesets
  to speedup testing.

• MSVC Compiler requires the C++ 20 Standard

• Systemtests: Some symlinked files with identical content have been
  split up into multiple files, as on windows the linking from the
  CMAKE_BINARY_DIR to the original files does no work.

• Every ctest call needs to set the configuration, i.e.
  ctest --build-config Debug/Release ...<other ctest options>

Please check

• Short description and the purpose of this PR is present above this paragraph
• Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

• Git Workflow
• Automatic Sourcecode Formatting
• Check your commit messages
• Boy Scout Rule

Checklist for the reviewer of the PR (will be processed by the Bareos team)

Make sure you check/merge the PR using devtools/pr-tool to have some simple automated checks run and a proper changelog record added.

General

• Is the PR title usable as CHANGELOG entry?
• Purpose of the PR is understood
• Commit descriptions are understandable and well formatted
  Check backport line
  Required backport PRs have been created

Source code quality

• Source code changes are understandable
• Variable and function names are meaningful
• Code comments are correct (logically and spelling)
• Required documentation changes are present and part of the PR