Test: e2e test for teams

[Ajen07]

Description

• Added e2e tests for Teams controller

Issue link

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature updates / changes
• Tests
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Tested with yarn test:docker

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the change log

[cherylli]

looks good, just need to add 403 tests for non admin users for some routes

[timDeHof]

All tests passed. The test file is well-structured and follows good practices for e2e testing in Nestjs. However, I added a few suggestions to the code that could improve the code quality.

[timDeHof]

Looks good, All tests passed

[JoshuaHinman]

All tests passed and code looks great

[cherylli]

ran all the tests, all good. Thanks for adding the 403

[timDeHof]

All the tests passed!