kfdtest: Consolidate logic for ASSERT vs EXPECT

ASSERT failures result in immediate termination of the test. EXPECT
returns a failure but continues execution. Reserve ASSERT for required
functionality (node initialization, queue creation, etc) where the rest
of the test cannot run if that call fails. Use EXPECT everywhere else

Change-Id: I1c11326fc3ae22b50fa83b07b3b49af1e1f4e69e


[ROCm/ROCR-Runtime commit: fe33461622]

projects/rocr-runtime/tests/kfdtest/src/KFDCWSRTest.cpp

@@ -135,7 +135,7 @@ TEST_F(KFDCWSRTest, BasicTest) {
 
         PM4Queue queue1, queue2;
 
-        EXPECT_SUCCESS(queue1.Create(defaultGPUNode));
+        ASSERT_SUCCESS(queue1.Create(defaultGPUNode));
 
         Dispatch *dispatch1, *dispatch2;
 
@@ -153,7 +153,7 @@ TEST_F(KFDCWSRTest, BasicTest) {
         // Submit the shader, queue1
         dispatch1->Submit(queue1);
         // Create queue2 during queue1 still running will trigger the CWSR
-        EXPECT_SUCCESS(queue2.Create(defaultGPUNode));
+        ASSERT_SUCCESS(queue2.Create(defaultGPUNode));
         // Submit the shader
         dispatch2->Submit(queue2);
         dispatch1->Sync();