Simple longevity tests

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Makefile

@@ -118,8 +118,8 @@ integration-test-debug-compose-down:
 
 
 longevity-test: generate-gokms-certs build-images install-gosdnc
-	rm -r longevity-tests/akms1-logs
-	rm -r longevity-tests/akms2-logs
+	rm -rf longevity-tests/akms1-logs
+	rm -rf longevity-tests/akms2-logs
 	docker compose -f longevity-tests/docker-compose.yml down
 	docker compose -f longevity-tests/docker-compose.yml up -d
 	echo "Will add devices, can take a while"
@@ -167,7 +167,7 @@ generate-etsi-rest-server:
 
 # Warning: Depending on your go and development configuration might also clean caches, modules and docker containers from your other projects.
 clean:
+	docker system prune -af
 	rm -rf $(BUILD_ARTIFACTS_PATH)
 	rm -rf $(TOOLS_DIR)
 	$(GOCLEAN)
-	docker system prune -af