feat: Remove minimum of 2 teams for making an Org

[kart1ka]

What does this PR do?

• Fixes [CAL-3835] Remove minimum of 2 teams for making an Organisation #15263
• Fixes CAL-3835 (Linear issue number - should be visible at the bottom of the GitHub issue description)

/claim #15263

https://www.loom.com/share/0c963c9c3e41429e9627ff2f8adbfe67?sid=c4fb3359-a4f3-45f9-a243-c71a61b06fab

The error (Could not invite the user as he might be part of another organization) thrown in Step-5 exists in the main branch as well. It probably occurs because the org owner is already added to the new org but we try to add it again, in Step-5, when we move the existing team, of which the owner is a part, to the new org.
Apart from that, the org is created successfully and everything else seems to work fine.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected)
• I have added a Docs issue here if this PR makes changes that would require a documentation change
• I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

[vercel]

@kart1ka is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link.

[graphite-app]

Graphite Automations

"Add community label" took an action on this PR • (05/30/24)

1 label was added to this PR based on Keith Williams's automation.

"Add consumer team as reviewer" took an action on this PR • (05/30/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[PeerRich]

hey @kart1ka can you record a loom video?

[kart1ka]

hey @kart1ka can you record a loom video?

Hi @PeerRich

Here is the loom video:
https://www.loom.com/share/0c963c9c3e41429e9627ff2f8adbfe67?sid=c4fb3359-a4f3-45f9-a243-c71a61b06fab

The error (Could not invite the user as he might be part of another organization) thrown in Step-5 exists in the main branch as well. It probably occurs because the org owner is already added to the new org but we try to add him again, in Step-5, when we move the existing team, of which the owner is a part, to the new org.
Apart from that, the org is created successfully and everything else seems to work fine.

[hariombalhara]

Thanks for the PR 🙏

Even though your changes work, but we should use a different approach to solve it as suggested.