[dashboard] make sure all team route under /t

[mustard-mh]

Description

See also #15002 (comment)

Related Issue(s)

Fixes #15002 (comment)

How to test

• Open preview env
• Go to settings -> Personal Access Token, check if navigation elements are correct

❓ What should we test to prevent regression of /t/<xxx> and <xxx>

Release Notes

NONE

Documentation

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-mustard-mh-design-improvements-15002.1 because the annotations in the pull request description changed
(with .werft/ from main)

[mustard-mh]

❓ What should we test to prevent regression of /t/<xxx> and <xxx>

@easyCZ @laushinka @gtsiolis do you have any cases that need to be covered about team routers?

[laushinka]

do you have any cases that need to be covered about team routers?

• /projects
  • /branches
  • /prebuilds
  • /settings
• /members
• /usage
• /settings

How about we write unit tests for these? Also happy to pair if you'd like.

[mustard-mh]

Changes make sure the navigation buttons only appear when the route is under /t or /projects. Not add test cases yet. We can do it in follow-up PR. cc @laushinka

Personal Projects

1. Personal projects

2. Personal projects with prebuild

Team

1. Team hello with member

2. Team hello with project prebuild

3. Team hello with project prebuild details

Personal Access Token

1. PAT Create

2. PAT Edit

[gtsiolis]

UX LGTM, @mustard-mh! 🔮

[laushinka]

Not add test cases yet. We can do it in follow-up PR.

Sure. LGTM - thanks for fixing this!