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

[AetherUnbound]

Description

Implementation plan for #431

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

Draft an implementation plan for determining how machine-generated labels will be conveyed in the API. This may leverage the accuracy and provider keys within the array of objects in the tags field. It should be relatively easy to expose the provider in the tags field on the API by adding it to the TagSerializer

Special care will need to be taken when determining how to handle multiple instances of a machine-generated tag. We will need to consider one of the following approaches for resolving this in Elasticsearch:

• Prefer creator-generated tags and exclude machine-generated tags
• Prefer machine-generated tags and exclude creator-generated tags
• Keep both tags, acknowledging that this will increase the score of a particular result for searches that match said tag
• Prefer the creator-generated tags, but use the presence of an identical machine-labeled tag to boost the score/weight of the creator-generated tag in searches