feat(cli): Symbolicate remote apple crash reports

[jjbayer]

#1900 added the ability to symbolicate apple crash reports with symbolicli in --offline mode. This PR extends the functionality to also support --online mode.

ref: #1884

[sentry]

Bug: The code classifies files starting with b"----" as Apple crash reports, but the downstream parser likely doesn't support this format, which will cause a runtime crash.
_{Severity: HIGH}

Suggested Fix

Remove the || &magic == b"----" check. Alternatively, if this format is valid, add test cases with fixtures that start with b"----" to verify the parser can handle them. Also, add documentation explaining what this format represents.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: crates/symbolicli/src/main.rs#L275

Potential issue: The code adds a check for `b"----"` to identify Apple crash reports.
When a file with these magic bytes is encountered, it's passed to
`AppleCrashReport::from_reader()`. However, there is no evidence that the
`apple_crash_report_parser` crate supports this format. This will likely cause the
parser to fail, resulting in an unhandled error that crashes the `symbolicli` tool with
the message "failed to parse apple crash report". This can be triggered in online mode
if a Sentry event has an `event.applecrashreport` attachment starting with `----`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}