profiler.id is always attached, even if ProfilingManager is rate-limiting

This has been observed for Perfetto Profiling in our demo app, where a trace had a `profiler.id` set, but the actual profile was missing.

When linking traces and profiles, we link them unconditionally, e.g. here: [https://github.com/getsentry/sentry-java/blob/bcd3e76a8033a30cf291fc84c726d40205b21db2/sentry/src/main/java/io/sentry/SentryTracer.java#L552]()

This stems from `ProfilingManager`, where requests can be rate-limited, and rejections are only reported via async profiling result. Or in other words `PerfettoProfiler.start()` will always return true, and only `processResult` at a later point will be able to detect rate limiting.

從 sentry/src/main/java/io/sentry/SentryTracer.java 中連結的 trace/profile 關聯處開始，然後追蹤 ProfilingManager 和 PerfettoProfiler.start() 直到 processResult。確認受速率限制的 profiling 結果如何回報，並驗證相應的 profile 缺失時 traces 不會取得 profiler.id。

由索引模型根據 Issue 內容生成。