Move OAV screen files to components

While refactoring the OAV screen, the code should've been moved to the components as they're all components that should be combined in the screen and to keep the screens focused on just UI presentation.

Plus it will give us a chance to ensure none of the components are too coupled.

Locate the OAV screen files and the existing components directory, then read how the screen assembles its current UI. Move the relevant screen code into components while keeping the screen focused on presentation, and verify that the components are not unnecessarily coupled.

Written by the indexing model from the issue text.