Adding the title and icon does indeed make sense, but only when the auth buttons are abstracted out of the topnavigation widget. Otherwise, people doing widget development will be given properties that can't be used inside of the context of their widget. I don't see a need to do the abstraction at this point, but can make that part of this ticket if you insist.

Looping over the external strategies has some drawbacks as well. I actually think it makes the template a bit harder to read/understand. Rendering each external strategy is already a single line in the template, but it does allow control over display/special cases/ordering. When looping over the external strategies object, the ordering becomes random and creates an inconsistent user experience.

Currently, the top navigation template already needs to be aware of all individual auth strategies in order to calculate things like `hasSingleInstitutionalAuth`. Therefore, a change to the template will be required anyway when a new strategy is added (which is a rare event anyway).