[ReportActionsView] Isolate view/render logic from the "unread business logic"

[marcaaron]

Problem

ReportActionsView has grown in size and has many responsibilities which can make it hard to reason about. There is logic that is primarily related to rendering the list of messages in a chat mixed together with several other things e.g.

• Performance code for timing the rendering of this list
• Floating message counter logic
• New marker logic
• Render methods for FlatList
• Data fetching
• etc.

It's a lot.

Solution

Move the stuff related to FlatList and anything that can be separated from the more complicated logic related to setting an "unread" message out of the ReportActionsView and into a ReportActionsList component that will simply render the chat list.