Request: Eagon interface updates after atlas rework

With the move to generic maps items and memory threads as a currency, Eagon is more flexible. However his interface still relies on outdated expectations from before. This thread attempts to capture feedback about the Eagon/memory thread interface to improve player workflow.

1. As Eagon opens a specific map, the interface SHOULD display the name of the map that will be opened. The current interface has swapped to use the generic map item, but there no longer any indication which map layout will be opened without opening the Atlas interface to view the memory thread. The primary impact is when users want to swap between Eater/Exarch and Maven for the final map in the thread sequence.

2. Eagon interface SHOULD more clearly show the selected memory thread modifiers. These could be displayed on the map item, but they could be displayed in a separate box. Displaying them separately from the map item will amplify the impact of the modifiers selected to users.

4. Eagon interface SHOULD use the new map + fragment layout. Eagon is limited to 3 fragment slots, and also maintains the old square layout. The updated layout w/ clear map slot + modifier fragments is a better design and should be ported back to the Eagon interface.

3. Eagon interface COULD display the entire memory chain and the players progress along it. When users interact with Eagan, they are likely doing the entire memory chain in a single sequence, so showing a linear progress sequence would allow users to track progress more clearly.

5. Eagon interface COULD be merged w/ the main map interface. Maintaining the a separate interface through an NPC rather than through the main map interface introduces something additional to track. It might be possible to implement memory threads in a similar manner to an Astrolabe region with the final map working in a similar mapper to Astrolabe vaults.