Update agentOccupationId Field to also map to Role (from 1092)

[gigamorph]

Problem Description

Some records for agents are classified as a type called "Role" this is a distinct classification from "Occupation", but they are used interchangeably. Currently there is a field for "Occupation" but not for "Role". We would like to update the agentOccupationId Field to also contain a path for "Role".

Expected Behavior

Searching with the updated agentOccupationId field returns agents which have a Role matching the search, in addition to agents that have an Occupation that matches the search.

Prerequisites

• [x] Create a pipeline data constant for Role. - https://git.yale.edu/LUX/pipeline/issues/505

Prerequiste For

• https://git.yale.edu/lux-its/lux-web/issues/1844

---

Based on Bugherd #1744

[roamye]

@clarkepeterf - the prerequiste for this ticket has been complete as https://git.yale.edu/LUX/pipeline/issues/505 is closed. Is this OK to add onto 7/22 milestone? or does this need to be pushed further out?

Lmk, this is blocking FE 45.

cc: @kamerynB

[clarkepeterf]

@roamye I think it should be good to go, I just need one bit of information - @kkdavis14 can you tell me what AATis used when an agent is classified as a Role?

[kkdavis14]

@clarkepeterf 300435108