LUX should be able to redirect old YUIDs to new ones from a mapping (from 1477)

Problem Description: The pipeline sometimes merges YUIDS when two records are determined to be about the same entity. For example currently we have for Larry:

Expected Behavior/Solution: A future pipeline might merge these together. However, if someone has bookmarked (e.g. in a list of people in LUX who work at Yale) one of the records that gets merged, it would be nice if it redirected to the merged URI rather than getting a 404. The pipeline can record when it merges YUIDs together and generate a map from the old to the new. When the old URI is requested, it could redirect to the new one.

Requirements: List of details required for the completion of the issue or requirements for the feature/bug. This can also include requirements that lie outside of the teams such as new design docs or clarification from an outside source.

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

[ ] To be designed where this occurs, and how the mapping is to be sent from pipeline to that place.
[ ] Examples for testing
[ ] Wireframe/Mockup - Mike
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

Example endpoints from LUX to use for development and testing, if applicable.

Dependencies/Blocks:

[x] Blocked By: https://git.yale.edu/LUX/pipeline/issues/358

Related Github Issues:

Related links:

Wireframe/Mockup: Place wireframe/mockup for the proposed solution at end of ticket.

project-lux / lux-frontend

LUX should be able to redirect old YUIDs to new ones from a mapping (from 1477) #20