API - 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-admin#3793

[hustlernik]

@meetulr Please assign this issue.

[hustlernik]

I have done some research on plugin architecture, after creating a draft, I will share with you soon.

[hustlernik]

Also currently assigned issue to implement block functionality is almost done, so I will raise PR for that today.

[bandhan-majumder]

@meetulr assign please

[meetulr]

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

[bandhan-majumder]

@meetulr I think the current codebase of talawa-api has no plugin support by default. Nothing else is there to remove. The plugins it has right now are for Fastify which are irrelevant than the scope of the issue. Can you please take a look once

[meetulr]

Look in the develop branch, remove the plugin functionality from there.

[bandhan-majumder]

@meetulr I think I am a bit confused. Can you please clarify the doubts here;

1. Should I remove the code for develop or develop branch.
2. Should I do the same for develop or develop-postgres from talawa-admin

The plugin features are not migrated to postgres in develop-postgres as maybe they are broken. So @xoldd ignored them.

[meetulr]

The issue is for removing the code from the develop branch in the api.

And since it's present in both the branches in admin, you should remove it from both. So for admin, you can raise two prs, one for each branch.

[bandhan-majumder]

@meetulr okay.