Vulnerability Report: align pipeline status

What does this MR do and why?

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. Navigate to a vulnerability report
2. Verify that the pipeline status renders correctly on different viewport sizes

Note: To mock a sbom-pipeline apply the following diff:

diff --git a/ee/app/assets/javascripts/security_dashboard/components/shared/project_pipeline_status.vue b/ee/app/assets/javascripts/security_dashboard/components/shared/project_pipeline_status.vue
index 1b5849f9c188..747551f8b949 100644
--- a/ee/app/assets/javascripts/security_dashboard/components/shared/project_pipeline_status.vue
+++ b/ee/app/assets/javascripts/security_dashboard/components/shared/project_pipeline_status.vue
@@ -13,7 +13,24 @@ export default {
   },
   props: {
     pipeline: { type: Object, required: true },
-    sbomPipeline: { type: Object, required: false, default: null },
+    // sbomPipeline: {
+    //   type: Object,
+    //   required: false,
+    // },
+  },
+  data() {
+    // Mock SBOM pipeline with realistic data for testing
+    return {
+      sbomPipeline: {
+        id: 987654,
+        createdAt: '2025-10-20T10:30:45Z',
+        path: '/gitlab-org/gitlab/-/pipelines/987654',
+        hasParsingErrors: false,
+        hasParsingWarnings: false,
+        securityBuildsFailedCount: 0,
+        securityBuildsFailedPath: '/gitlab-org/gitlab/-/pipelines/987654/failures',
+      },
+    };
   },
   computed: {
     parsingStatusMessage() {

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #561396 (closed)