Fix Relation Names For agent relatedToEvent - supports FE 8

[clarkepeterf]

Problem Description:
There are no relation names for
Expected Behavior/Solution:
There are new relation names for the relationships returned from agent relatedToEvent:

'created-carriedBy-memberOf-usedForEvent': 'Created Works Carried by Objects Used At',
'encountered-memberOf-usedForEvent': 'Encountered Objects Used At',
'produced-memberOf-usedForEvent': 'Produced Objects Used At',
'published-carriedBy-memberOf-usedForEvent': 'Published Works Carried by Objects Used At',
'subjectOfAgent-carriedBy-memberOf-usedForEvent': 'Is the Subject of Works Carried by Objects Used At'

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.

- [ ] 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:

Reviewable via the frontend issue: Events: Related People and Groups (from 402)

Dependencies/Blocks:

• Blocking: Add HAL link for related People and Groups on Event pages - supports FE 8 lux-middletier#29
• Which also blocks: Events: Related People and Groups (from 402) lux-frontend#8

Related Github Issues:

• Events: Related People and Groups (from 402) lux-frontend#8

Related links:

N/A

Wireframe/Mockup:
N/A

[clarkepeterf]

@prowns this is a very quick one and blocks a HAL link ticket- I'm tempted to just knock it out ASAP tomorrow, but putting in prioritization review for now

[roamye]

Approved per UAT

[roamye]

Looks good in prod, closing.