Feature/317 include collaborators project overview

[waltersajtos]

Description

Because of the redesign of the project overview page, we need the collaborators for every project.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• 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

Checklist

• My code follows the style guidelines of this project
• I did not update API Controllers, if I did, I added/changed Postman tests
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I updated the changelog with an end-user readable description
• I assigned this pull request to the correct project board to update the sprint board

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.
These steps will be used during release testing.

1. Make a GET request to /api/project
2. The response should include the collaborators

Link to issue

#317

Closes: #317

[RubenFricke]

I noticed you didn't add a description for this pull request. I understand it's a lot of work to add a description for a small issue like this. However, I don't think we need to skip them, I think it's important to create a description for small issues as well 😄 .

And another small thing: do you think this is a New feature? Don't you think it's rather a bugfix (which fixes in issue for the frontend?).

Overall the code looks good and works like a charm

[waltersajtos]

I noticed you didn't add a description for this pull request. I understand it's a lot of work to add a description for a small issue like this. However, I don't think we need to skip them, I think it's important to create a description for small issues as well 😄 .

And another small thing: do you think this is a New feature? Don't you think it's rather a bugfix (which fixes in issue for the frontend?).

Overall the good looks good and works like a charm

You are right, I edited the description but forgot to save it :)
I wasn't sure what to call it, since it isn't really a bug because the behavior was expected.