fix: ensure app listens on IPv4/tcp ports

[LRTNZ]

Due to a change in the way the app dependency works, not specifying
an address (even just '0.0.0.0') means that the program would listen to
an IPv6 address/port, instead of IPv4, which nearly everything is still
configured for. This meant that the client could not see the media
scanner. This commit fixes that, by making the app dependency listen
on an IPv4 address/port.

[Julusian]

I have reverted this in v1.1.1, as it breaks the default configuration on windows.
On windows localhost resolves to ::1 with a higher priority than 127.0.0.1, resulting in caspar attempting to connect to the scanner over ipv6, failing and then retrying over ipv4.

Additionaly, on both windows10 and ubuntu22.04, with this reverted I am able to access the scanner over both http://127.0.0.1:8000, http://[::1]:8000 in chrome, so it looks like they are both binding well enough to ipv4 and ipv4.
Perhaps this bind behaviour changed as part of the nodejs update? Or during an os update? Either way it looks to no longer be an issue