feat: have the Queue-Worker app start up a simple web server for metrics

This is somewhat experimental and temporary
(hence the port hack).

Author: SpraxDev

src/boot/QueueWorkerApp.ts

@@ -1,11 +1,14 @@
 import { container } from 'tsyringe';
 import CliArgumentProvider from '../cli/CliArgumentProvider.js';
+import AppConfiguration from '../config/AppConfiguration.js';
 import ContinuousQueueWorker from '../import_queue/worker/ContinuousQueueWorker.js';
 import TaskScheduler from '../task_queue/TaskScheduler.js';
+import FastifyWebServer from '../webserver/FastifyWebServer.js';
 import App from './App.js';
 
 export default class QueueWorkerApp implements App {
   private taskScheduler: TaskScheduler | undefined;
+  private webServer: FastifyWebServer | undefined;
 
   async boot(): Promise<void> {
     if (CliArgumentProvider.determineLeftoverArgs().length !== 0) {
@@ -20,11 +23,21 @@ export default class QueueWorkerApp implements App {
       .resolve(ContinuousQueueWorker)
       .start();
 
+    // DEBUG
+    const appConfig = container.resolve(AppConfiguration);
+    this.webServer = container.resolve(FastifyWebServer);
+
+    await this.webServer.listen(appConfig.config.serverInterface, appConfig.config.serverPort + 100);
+    // DEBUG END
+
     console.log('\nQueue worker finished initialization');
   }
 
   async shutdown(): Promise<void> {
     this.taskScheduler?.dispose();
     this.taskScheduler = undefined;
+
+    await this.webServer?.shutdown();
+    this.webServer = undefined;
   }
 }

src/minecraft/server/ping/AbstractMinecraftServerPing.ts

@@ -35,6 +35,7 @@ export type PotentialServerStatus = {
   favicon?: string;
 }
 
+// TODO: Handle proxy connection errors and introduce retry mechanism
 export default abstract class AbstractMinecraftServerPing {
   private static readonly socksProxyConnector = new SocksProxyServerConnector();
   private static socksProxyPool: RoundRobinProxyPool<SocksProxyServer> | undefined;