Fix pdb-none.test expectaions for output of pdbutil

[sbc100]

Summary

pdbutil output seems to have changed to include more fields.
This change makes pdb-none.test less fregile in the face
of such changes by using CHECK: rather than CHECK-NEXT:.
I'm assuming the extra interviening fields should not
trigger failure.

[sbc100]

I see you already fixed the failure in r305260 but thought maybe this fix might still be desirable?

[sbc100]

sgtm

test/COFF/pdb-none.test

 # RUN: yaml2obj < %p/Inputs/pdb1.yaml > %t1.obj
 # RUN: yaml2obj < %p/Inputs/pdb2.yaml > %t2.obj
 # RUN: lld-link /debug /debugtype:pdata /pdb:%t.pdb /dll /out:%t.dll /entry:main /nodefaultlib \
 # RUN:   %t1.obj %t2.obj
 
 # RUN: llvm-pdbutil pdb2yaml -pdb-stream %t.pdb | FileCheck %s
 
-# CHECK:      PdbStream:
-# CHECK-NEXT:   Age:             0
-# CHECK-NEXT:   Guid:            '{00000000-0000-0000-0000-000000000000}'
-# CHECK-NEXT:   Signature:       0
-# CHECK-NEXT:   Features:        [ VC140 ]
-# CHECK-NEXT:   Version:         VC70
-
+# CHECK: PdbStream:
+# CHECK:   Age:             0
+# CHECK:   Guid:            '{00000000-0000-0000-0000-000000000000}'
+# CHECK:   Signature:       0
+# CHECK:   Version:         VC70