chore: Stop using secureblue for integration testing

This would occasionally cause tests to fail cause SecureBlue would rightfully make changes to their code. We shouldn't be relying on this anymore as it was a crutch to lean on when we were first starting this project

integration-tests/Earthfile

@@ -3,7 +3,6 @@ PROJECT blue-build/cli
 
 all:
 	BUILD +test-image
-	BUILD +test-secureblue
 	BUILD +test-legacy-image
 	BUILD +build
 	BUILD +rebase
@@ -24,20 +23,6 @@ test-legacy-image:
 
 	DO +RUN_TESTS
 
-test-secureblue:
-	FROM +build-template --src=template-secureblue
-	WORKDIR /tmp/test
-	COPY ./test-scripts/secureblue/*.sh ./
-
-	DO +RUN_TESTS
-
-test-secureblue-ucore:
-	FROM +build-template --src=template-secureblue-ucore
-	WORKDIR /tmp/test
-	COPY ./test-scripts/secureblue/*.sh ./
-
-	DO +RUN_TESTS
-
 build-template:
 	ARG --required src
 	FROM DOCKERFILE \
@@ -56,18 +41,6 @@ template-legacy-containerfile:
 
 	SAVE ARTIFACT /test
 
-template-secureblue:
-	FROM +secureblue-base
-	RUN bluebuild -vv generate -o Containerfile recipes/general/recipe-silverblue-nvidia.yml
-
-	SAVE ARTIFACT /test
-
-template-secureblue-ucore:
-	FROM +secureblue-base
-	RUN bluebuild -vv generate -o Containerfile recipes/server/recipe-server-main.yml
-
-	SAVE ARTIFACT /test
-
 build:
 	FROM +test-base
 
@@ -90,14 +63,6 @@ switch:
 	RUN mkdir -p /etc/bluebuild && touch $BB_TEST_LOCAL_IMAGE
 	RUN bluebuild -vv switch recipes/recipe.yml
 
-secureblue-base:
-	FROM +test-base
-
-	RUN rm -fr /test
-	GIT CLONE https://github.com/secureblue/secureblue.git /test
-
-	DO +GEN_KEYPAIR
-
 legacy-base:
 	FROM ../+blue-build-cli-alpine
 	RUN apk update --no-cache && apk add bash grep jq sudo coreutils