Centralize Translation Functions for Common and Error Keys

[pranshugupta54]

Note: This issue is part of my project for translations

Is your feature request related to a problem? Please describe.

Currently, translations for common keys are repeated across different screens in the frontend codebase. This leads to redundancy, makes maintenance difficult, and increases the risk of inconsistencies in translations.

Describe the solution you'd like

I propose creating separate functions for handling translations of common keys. These functions would be reused across different screens, ensuring consistency and reducing redundancy. This approach will centralize the translation logic, making it easier to update and manage.

Describe alternatives you've considered

1. Continue with the current approach: This option was dismissed as it leads to repetitive code and makes updates more cumbersome.
2. Use a third-party library: While this could standardize translations, it might introduce unnecessary complexity and dependencies.

Approach to be followed (optional)

1. Identify common keys: Review the current codebase to identify frequently used translation keys.
2. Create translation functions: Develop functions for these common keys and place them in a dedicated module.
3. Refactor existing code: Replace repeated translation keys with calls to the new functions.

Additional context

Centralizing translations will not only improve code maintainability but also enhance the consistency of the user experience.
Folder structure:

Potential internship candidates

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