ADMIN - Remove Legacy Plugin Code

[meetulr]

Describe the issue

The current plugin system does not meet our requirements in terms of functionality and scalability. We plan to implement an intuitive, robust and scalable plugin architecture with this GSoC project.

Describe the solution

Remove any existing code related to the plugin functionality.

Additional Context

Companion issue: PalisadoesFoundation/talawa-api#3337

[hustlernik]

@meetulr Please assign.

[meetulr]

@hustlernik, you’re already assigned to 3 issues. Our policy allows a maximum of 2 issues per contributor.

[bandhan-majumder]

@meetulr please assign. Please unassign me this issue to meet 2 issue criteria

[meetulr]

If you're no longer working on an issue, you can mention it there and unassign yourself.

[meetulr]

@bandhan-majumder Keep in mind the PR for admin should be merged first or it may cause things to break.

[bandhan-majumder]

@meetulr

Sure. And after that I may have to wait for talawa repo to remove legacy code before removing it in api too I guess.

[meetulr]

You can raise the prs simultaneously. It's just that the frontend ones should be merged first.

[bandhan-majumder]

@meetulr there are user level authorization of creating/blocking plugins. Should I remove them too from schema?

example:

[meetulr]

Yes, everything relevant.

[bandhan-majumder]

@meetulr @palisadoes

as we do not have full api support, I have removed the code with keeping the merged PR #3804 in mind (related files).
I have checked both with change and without change, the state and the errors are same. And that made me confident that the changes will not break any existing code/feature. I have tried it multiple times. LMK if any changes are still required.

[bandhan-majumder]

@palisadoes @meetulr

I missed a return filed to remove in develop branch. Added in the recently mentioned PR.

[Cioppolo14]

Reopening this issue until this new PR is complete.