Fix POST voyages/teams/{teamId}/techs bug

[JoshuaHinman]

Description

This PR fixes a bug in which a user can create a new tech for a category that doesn't belong to their team.

Issue link

Fixes # 86b2n3gbr

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?

yarn test

In swagger, verified that creating a tech within another team's category throws an error:

• login as [email protected]
• create tech with teamId: 1, techCategoryId: 51, "voyageTeamMemberId": 1

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

[andram11]

I think that techs.e2e-spec test should also be updated with a test case for this scenario

[cherylli]

@JoshuaHinman could you please resolve merge conflicts when you have a chance? Thanks!

[cherylli]

Got a failed test probably merge error

Everything else works

[Ajen07]

Tested the changes in Swagger, the issue has been resolved, and all tests have successfully passed.

fixed

[cherylli]

I will fix the changelog when I merge my latest PR, too many different changelog versions now 😂