Add ability to mark policy as critical. (#8896)

cmd/fleetctl/testdata/expectedHostDetailResponseJson.json

@@ -62,7 +62,8 @@
         "resolution": "Some resolution",
         "team_id": 1,
         "updated_at": "0001-01-01T00:00:00Z",
-        "created_at": "0001-01-01T00:00:00Z"
+        "created_at": "0001-01-01T00:00:00Z",
+        "critical": false
       },
       {
         "id": 2,
@@ -76,7 +77,8 @@
         "response": "fails",
         "team_id": null,
         "updated_at": "0001-01-01T00:00:00Z",
-        "created_at": "0001-01-01T00:00:00Z"
+        "created_at": "0001-01-01T00:00:00Z",
+        "critical": false
       }
     ],
     "status": "offline",

cmd/fleetctl/testdata/expectedHostDetailResponseYaml.yml

@@ -51,6 +51,7 @@ spec:
       team_id: 1
       created_at: "0001-01-01T00:00:00Z"
       updated_at: "0001-01-01T00:00:00Z"
+      critical: false
     - author_email: "alice@example.com"
       author_id: 1
       author_name: Alice
@@ -63,6 +64,7 @@ spec:
       team_id: null
       created_at: "0001-01-01T00:00:00Z"
       updated_at: "0001-01-01T00:00:00Z"
+      critical: false
   policy_updated_at: "0001-01-01T00:00:00Z"
   public_ip: ""
   primary_ip: ""