Android FileObserver must handle envelope item types user feedback and attachments.

Currently, Attachments and User Feedback if written to the directory the Android filewatcher uses to capture events from other layers (like react-native, native, flutter), are not captured.

The relevant code is here:

Ideally, this would be refactored to no longer call captureEvent. It's still there because through this method the event gets enriched with more context like device data, and scope data, if the event wasn't captured on a previous device run as the scope data would have been different. This is done through a Hint created by the FileObserver (only triggers during the app execution, which is a different code path of capturing cached errors on startup.