Use Environment.ProcessPath instead of GetCurrentProcess().MainModule.FileName

GetCurrentProcess().MainModule.FileName is expensive, Environment.ProcessPath added in net6

(cherry picked from commit f928ee7cad304115a002da00e218fb987e02b279)

Close #2260

src/NzbDrone.Common/ServiceProvider.cs

@@ -65,7 +65,7 @@ namespace NzbDrone.Common
 
             var args = $"create {serviceName} " +
                 $"DisplayName= \"{serviceName}\" " +
-                $"binpath= \"{Process.GetCurrentProcess().MainModule.FileName}\" " +
+                $"binpath= \"{Environment.ProcessPath}\" " +
                 "start= auto " +
                 "depend= EventLog/Tcpip/http " +
                 "obj= \"NT AUTHORITY\\LocalService\"";

src/NzbDrone.Host/Bootstrap.cs

@@ -47,7 +47,9 @@ namespace NzbDrone.Host
         {
             try
             {
-                Logger.Info("Starting Readarr - {0} - Version {1}", Assembly.GetCallingAssembly().Location, Assembly.GetExecutingAssembly().GetName().Version);
+                Logger.Info("Starting Readarr - {0} - Version {1}",
+                            Environment.ProcessPath,
+                            Assembly.GetExecutingAssembly().GetName().Version);
 
                 var startupContext = new StartupContext(args);