Add labels to the E2E tests

[jenting]

Description

Add labels to the E2E tests, the idea/concept of labels is

• Add team label to the E2E tests to indicate the test belongs to which team, either IDE, workspace, etc. Therefore, we could run the label filter by each team without having to enter each test folder.
• Add a component label to the E2E tests to indicate the test belongs to which Gitpod component (if possible).

Related Issue(s)

#8799

How to test

# It should only run the E2E tests with the label `team=workspace`, i.e., the E2E tests belong to the workspace team.
go test -v ./... \
  -kubeconfig=/home/gitpod/.kube/config \ 
  -namespace=<namespace> \
  -labels "team=workspace" 

# It should only run the E2E tests with the label `team=IDE`, i.e., the E2E tests belong to the IDE team.
go test -v ./... \
  -kubeconfig=/home/gitpod/.kube/config \ 
  -namespace=<namespace> \
  -labels "team=IDE" 

Release Notes

None

Documentation

No

[jenting]

After discussing with Kyle, this one is no more needed.
Close it.

[kylos101]

Thanks, @jenting ! There might be a need for this in the future? So I appreciate the effort you put into this PR. For now, the thought is, we can run tests associated with component binaries, as the workspace team owns certain components.

If we run into an issue where a component has shared tests (tests for 2 or more teams), then we may want to consider labels? Alternatively, that would also be a good opportunity to suggest moving the test to a separate path, so it does not share with workspace binaries. 😄