[userTypeFix] Removal of adminApproved field

[pranshugupta54]

Describe the bug

• adminApproved field is not being used anymore after the change in userType.
• Remove all the code using it.

Actual behavior
Every feature should be working, tests and code coverage.

Screenshots
NA

Additional details

1. We are using userRegistrationRequired bool for checking approval in Org.
2. membershipRequests array for list of pending users in Org.
3. adminApproved was earlier used for orgs but it's global.
4. All tests must pass and be valid
5. No other functionality must be affected

References:

1. [userTypeFix] Removal of adminApproved field talawa-api#2122
2. https://thepalisadoes-dyb6419.slack.com/archives/C01RPC00K0D/p1711717178931399

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

[disha1202]

I would like to work on this

[disha1202]

Also, are we sure this needs to be removed.

If in future we're planning to add the newMemberApprovalsRequired flag for approvals to join a community (i.e. not being able to access the user the admin portal unless approved by an admin or super admin).

Then we'll need a field i.e. adminApproved to track whether the user is approved or not. This field can be set to true in the default case.

we'll have to implement it again.

[palisadoes]

We already have the userRegistrationRequired flag as discussed in the slack conversation.

[disha1202]

We already have the userRegistrationRequired flag as discussed in the slack conversation.

Okay