[llvm] [NFC][AMDGPU] Automate any_extend_vector_inreg.ll check line generation (PR #145013)

[LLVM Continuous Integration via llvm-commits]

llvm-ci wrote:

LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib` running on `gribozavr4` while building `llvm` at step 6 "test-build-unified-tree-check-clang".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/60/builds/30761

<details>
<summary>Here is the relevant piece of the build log for the reference</summary>

```
Step 6 (test-build-unified-tree-check-clang) failure: test (failure)
******************** TEST 'Clang :: Analysis/ftime-trace.cpp' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
/b/1/llvm-x86_64-debian-dylib/build/bin/clang -cc1 -internal-isystem /b/1/llvm-x86_64-debian-dylib/build/lib/clang/21/include -nostdsysteminc -analyze -analyzer-constraints=range -setup-static-analyzer -analyzer-checker=core /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp -ftime-trace=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.raw.json -ftime-trace-granularity=0 -verify # RUN: at line 1
+ /b/1/llvm-x86_64-debian-dylib/build/bin/clang -cc1 -internal-isystem /b/1/llvm-x86_64-debian-dylib/build/lib/clang/21/include -nostdsysteminc -analyze -analyzer-constraints=range -setup-static-analyzer -analyzer-checker=core /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp -ftime-trace=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.raw.json -ftime-trace-granularity=0 -verify
"/usr/bin/python3.9" -c 'import json, sys; print(json.dumps(json.load(sys.stdin), indent=4))' < /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.raw.json > /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json # RUN: at line 2
+ /usr/bin/python3.9 -c 'import json, sys; print(json.dumps(json.load(sys.stdin), indent=4))'
/b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck --input-file=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json --check-prefix=CHECK /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp # RUN: at line 3
+ /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck --input-file=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json --check-prefix=CHECK /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp
/b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp:34:11: error: CHECK: expected string not found in input
// CHECK: "name": "Total CheckerManager::runCheckersForStmt (Pre)",
          ^
/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json:2562:3: note: scanning from here
 }
  ^
/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json:2738:2: note: possible intended match here
 "name": "Total CheckerManager::runCheckersForStmt (Post)",
 ^

Input file: /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/Analysis/Output/ftime-trace.cpp.tmp.formatted.json
Check file: /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/Analysis/ftime-trace.cpp

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
         2557:  "dur": 1072, 
         2558:  "name": "Total dispatchWorkItem PostStmt", 
         2559:  "args": { 
         2560:  "count": 31, 
         2561:  "avg ms": 0 
         2562:  } 
check:34'0       X error: no match found
         2563:  }, 
check:34'0     ~~~~
         2564:  { 
check:34'0     ~~~
         2565:  "pid": 3765398, 
check:34'0     ~~~~~~~~~~~~~~~~~
         2566:  "tid": 3765405, 
check:34'0     ~~~~~~~~~~~~~~~~~
         2567:  "ph": "X", 
check:34'0     ~~~~~~~~~~~~
            .
            .
...

```

</details>

https://github.com/llvm/llvm-project/pull/145013