Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend

[AetherUnbound]

Description

Implementation plan for #431

Context: https://docs.openverse.org/projects/proposals/rekognition_data/20240320-project_proposal_rekognition_data.html#frontend

Related to #4038, draft an implementation plan for determining how machine-generated labels will be conveyed in the frontend. We already have some machine-generated tags in the API, and so we will see the affects of this IP immediately (irrespective of #4038, though possibly augmented by the use of tags.provider in addition to tags.accuracy).

Similar to the API, it may also be useful to share the label accuracy with users (either visually or with extra content on mouse hover) along with its provider (for cases where we may have multiples of the same machine-generated tags from different sources). It would be beneficial to have a page much like our sensitive content explanation (either similarly available in the frontend or on our documentation website) that describes the nature of the machine generated labels, the means by which they were determined, and how to report an insensitive label.