Inter-interface Navigation Component(s)

We have made every AI angry with `#projectManagementBtn`. It's a copy and pasted HTML + CSS solution across interfaces and components to navigate back to project management. It occurred because every edit-project-data related interface needs a link back into project-management-home so the user doesn't get lost.

We know this mechanic will be repeated here and in other places. We even planned for it with the `tpen-gui-action-link` and other components in the `tpen-gui-*` space. Maybe it is time to take a hard look at these navigational moments and make a decision for what to do when we need the same one or multiple across different interfaces and components.

Think hard about how to componentize the use of the buttons included in interfaces and components that link back to /project/manage.

Consider that this will be repeated for links into other interfaces and components as they are designed. Let this mechanic work for any link out, not just /project/manage.

The component could be used multiple times on the same page to handle multiple links out. For example, /project/options should have two - one to go to /project/transcribe and one to go /project/manage.