Consume react-native dSYMs in staging and production CI workflows for Sentry symbolication

[MelvinBot]

Background

Follow-up to #86437.

Prebuilt iOS React Native artifacts are already consumed by our deploy scripts (they have a GitHub token available in their context), so no extra "enablement" is needed there. What's still missing is dSYM consumption: without the react-native dSYMs, crash reports for staging and production releases can't symbolicate react-native frames, so Sentry stack traces are incomplete.

Task

Consume the react-native dSYMs in our CI workflows (staging, production, and adhoc) so they're available during the Xcode archive step and can be uploaded to Sentry.

• react-native build utils download the dSYMs separately, then copy them into the xcframework.
• The Xcode archive extracts those dSYMs into a directory the Sentry build phase reads.
• Because dSYMs are large, add a cache step so they can be retrieved quickly during a workflow run.
• Remove the redundancy in the artifacts utility script so the package name is picked based on the platform and hybrid flags.

PR

Addressed by #98853.

[mateuuszzzzz]

PR is ready for a review