"AIV portal" improvements and evolution

AIV users and stakeholders must work with many services, UIs, and data (product documentation etc). A simple interface to discover and connect to these is therefore envisaged to be extremely valuable and was requested for PI21 by the Low AIV team (see https://confluence.skatelescope.org/display/TDT/LOW+AIV+Portal+Specification) 

Experiments in PI21 show the AIV portal has strong potential, but further improvements are now needed to achieve its true value.

To be discussed and updated at PI planning

High priority:

1. Populate remaining links (AIV SS or AIV teams)
2. Documentation, examples, and training for how to populate and update links (Stargazer)
3. Complete AD integration (Naledi, support from IT and/or Bang for AD roles?)
4. Improve filter behaviour for the role, environment & namespace selection (Naledi)
5. Add labels/tags to links: provide display and sorting options based on these (Stargazer)

Medium Priority:

1. Deployment solution: Cloud-based or Local to Mid/Low (Naledi with support from system team + Architects)
2. Review and provide advice for how to implement AD token pass through to underlying services; PoC / example with at least one service (Naledi + support from System team?)

Lower Priority:

1. Improve solution for link configuration and management (Stargazer)
2. Solution to save user settings between sessions (Stargazer)