fix: Enable Network Discovery and File Sharing by default (#420)

[hellodword]

fixes #420

Tested with the latest versions from https://www.microsoft.com/software-download/windows11 and https://www.microsoft.com/software-download/windows10

[hellodword]

@kroese This may cause security issues for normal users, I guess we should create a switch in the qemu image? Like:

if /storage/shared is mounted
   enable it
else
   disable it

I'm not familiar with the qemu layer of dockur, how do you think?

[hellodword]

And based on this feature, I want to create a new feature, it looks like:

        <SynchronousCommand>
          <Order>201</Order>
          <CommandLine>powershell.exe -sta -ExecutionPolicy Bypass -Command "\\host.lan\Data\FirstLogonCommands\sta\run-custom.ps1 *> C:\output-201.log"</CommandLine>
          <Description>run custom</Description>
        </SynchronousCommand>

loop the \\host.lan\Data\FirstLogonCommands and execute all of them(bat, ps1, and so on)

It'll improve the automation usage of dockur a lot. For example, all the #187 related users are able to always use the latest version of dockur, without maintaining a modified and outdated win11x64.xml locally.

How do you think? Once the security issue of this PR been solved, I'd love to create a draft PR for this :)

[kroese]

@hellodword It should not create any security issue while the container is in a bridge network (the default). Because no ports are forwarded in the compose file to allow Samba access, so other computers in the LAN can never access the machine, even with with Network Discovery / File Sharing enabled.

So unless somebody manually forwards the ports in bridge mode or puts the container in macvlan it will not be a problem.

[hellodword]

Great, glad to know that :)