copied the structure of energyservice test and changed it to fit for roombooking

@@ -0,0 +51,4 @@
+        /*what services/images that need to be build vary between different services, 
+        once a image is made you must CreateAsync() before usign it in a ContainerBuilder */
+        _postgres = new PostgreSqlBuilder("postgres:18.3-alpine3.23")
+        .WithImage("postgres:15-alpine")

@@ -0,0 +56,4 @@
+        .WithEnvironment("POSTGRES_PASSWORD", dbPassword)
+        .WithEnvironment("POSTGRES_DB", "sensors")
+        .WithEnvironment("POSTGRES_HOST_AUTH_METHOD", "trust")
+        .WithHostname("roombookingservice")

@@ -0,0 +91,4 @@
+
+        builder.ConfigureServices(services =>
+        {
+            /*currently services use diffrent DataSource names to connect to msqtt and similar thigns

@@ -0,0 +166,4 @@
+    {
+        /*Test if http requests work by just checking if health returns
+        prefixes can be different for services.*/
+        var response = await _httpClient.GetAsync("/roombooking/healthcheck");

@@ -0,0 +104,4 @@
+            services.AddSingleton(testDataSource);
+
+            /* We create a postgresql container, a place for databases exist but it seems to still need to be populated.
+            * This helps create a real database and not a mock database so all tests ran on it would work on the actual database druing run time.

@@ -0,0 +177,4 @@
+    [Fact]
+    public async Task Get_bookingData_Returns_Success_And_Data()
+    {
+        /* http request after populating with the table. Again the database table is real, just empty so we create it durign cotnainer building

@@ -0,0 +179,4 @@
+    {
+        /* http request after populating with the table. Again the database table is real, just empty so we create it durign cotnainer building
+        * and in tests we can populate the table. 
+        * There should be some way to populate them as normal usign your generators but testcontainers are fast, 

@@ -0,0 +181,4 @@
+        * and in tests we can populate the table. 
+        * There should be some way to populate them as normal usign your generators but testcontainers are fast, 
+        * once built they run the tests extremly quickly and then kill the contianers 
+        * so you propably don't even have time to passivly populate the containers.