[CK] Fix/suppress clang lifetimebound warnings with staging compiler. (#6550)

## Motivation

New changes from upstream llvm-project cause an avalanche of warnings in
CK. Gonna disable them by ignoring the
lifetime-safety-intra-tu-suggestions flag until a better permanent
solution is found.

## Technical Details

<!-- Explain the changes along with any relevant GitHub links. -->

## Test Plan

<!-- Explain any relevant testing done to verify this PR. -->

## Test Result

<!-- Briefly summarize test outcomes. -->

## Submission Checklist

- [ ] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

tile_engine/ops/common/utils.hpp

@@ -72,7 +72,8 @@ struct KernelInstance
 };
 
 template <typename Problem>
-std::ostream& operator<<(std::ostream& os, const KernelInstance<Problem>& obj)
+std::ostream& operator<<([[clang::lifetimebound]] std::ostream& os,
+                         const KernelInstance<Problem>& obj)
 {
     os << "{\n"
        << " \"name\": \"" << obj.name_ << "\",\n"
@@ -82,7 +83,7 @@ std::ostream& operator<<(std::ostream& os, const KernelInstance<Problem>& obj)
     return os;
 }
 
-std::ostream& operator<<(std::ostream& os, const PerformanceResult& result)
+std::ostream& operator<<([[clang::lifetimebound]] std::ostream& os, const PerformanceResult& result)
 {
     os << "{\n"
        << "   \"latency(ms)\": " << std::fixed << std::setprecision(2) << result.latency_ << ",\n"

tile_engine/ops/gemm/gemm_benchmark.hpp

@@ -26,7 +26,8 @@ struct GemmProblem
 
     bool structured_sparsity_;
 
-    friend std::ostream& operator<<(std::ostream& os, const GemmProblem& problem)
+    friend std::ostream& operator<<([[clang::lifetimebound]] std::ostream& os,
+                                    const GemmProblem& problem)
     {
         os << "{\n"
            << "   \"split_k\":" << problem.split_k_ << ",\n"