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.

Comece em sentry/src/main/java/io/sentry/SentryTracer.java, na associação vinculada entre trace e profile, e depois acompanhe ProfilingManager e PerfettoProfiler.start() até processResult. Confirme como os resultados de profiling sujeitos a limitação de taxa são reportados e verifique se as traces não recebem profiler.id quando o profile correspondente está ausente.

Escrita pelo modelo de indexação a partir do texto da issue.