Add optional chaining to handle cases where Component is undefined
during module loading due to circular dependencies.

Problem: When styled components are created at module load time,
circular dependencies can cause the Component parameter to be undefined
(e.g., AlertDropdown -> EdgeTouchableOpacity -> AirshipInstance -> AlertDropdown).
This resulted in 'Cannot read properties of undefined (reading displayName)' errors.

Solution: Use optional chaining (Component?.displayName) to safely
access displayName property, preventing TypeError during circular
dependency resolution.

Add error reporting functionality to AlertDropdown component:

- When error prop is provided, dropdown becomes persistent and shows
  Report Error button at bottom
- Report Error button tracks error to Sentry with userReportedError metadata
- After reporting, shows success state with checkmark and 'Report sent' message
- Auto-dismisses after 3 seconds to allow user to read confirmation
- Uses localized strings for button text and success message
- Disables dropdown onPress to prevent accidental dismissal during error state

The implementation uses styled components for the error UI elements,
which now work correctly thanks to the circular dependency fix in the
styled HOC.