Feat: Refactor for Project Role assignments for Team

[TomerHeber]

Solution

Part of #817. Will create another PR for refactoring the API.

1. Modifed the API code.
2. Updated unit tests.
3. Modified the resource code to use the new API.
4. Updated acceptance tests.

[razbensimon]

@TomerHeber @sagydr Do we need a non-patch upgrade here?
i wonder how a new tf plan will look like after apgrading

[TomerHeber]

@TomerHeber @sagydr Do we need a non-patch upgrade here? i wonder how a new tf plan will look like after apgrading

@razbensimon - the plan should remain the same. Is there a way to test it? I can do a new major version if it makes sense. WDYT?

[razbensimon]

if we can do it with a patch it is awesome, I just bring it up for you to test it.
meaning "upgrading" after having an existing project assignment in the state.
then try to:

1. plan/apply with no changes
2. delete assignment
3. change assignment
4. add assignment

EDIT:
mostly I afraid of the ProjectRole & Role renames. how it will effect the state/plans?

[razbensimon]

I think "api_client" should have only 3 methods, that serve all scopes for team (and additional 3 methods for users).
the methods are the upsert / remove / get assignments - corresponding to the API.

So each method will get the scopeId as an argument (aka environmentId, projectId, or organizationId. They are optional and only one of them should exist).
That's because all of those are the same API and routes.

meaning TeamProjectAssignmentCreateOrUpdate and TeamProjectAssignmentDelete should be removed. And we should not "drag" / keep the existence of the old deprecated APIs names.

WDYS?

[razbensimon]

the only scopes we haven't refactored yet - should preserve their methods here. Until we will refactor them too.
that's include:

1. org level user assignments
2. project level user assignments

[TomerHeber]

will be done in a follow-up PR.

[TomerHeber]

if we can do it with a patch it is awesome, I just bring it up for you to test it. meaning "upgrading" after having an existing project assignment in the state. then try to:

1. plan/apply with no changes
2. delete assignment
3. change assignment
4. add assignment

EDIT: mostly I afraid of the ProjectRole & Role renames. how it will effect the state/plans?

As discussed on Slack. Only concern is if someone had mistakenly applied multiple assignments on the same project and team. (Not supported in the UI).