Refactor: src/screens/OrgPost from Jest to Vitest

[VanshikaSabharwal]

Is your feature request related to a problem? Please describe.
This file is currently tested using Jest. As part of our migration to Vitest, we need to refactor this file's test cases to align with Vitest's syntax and features.

Acceptance Criteria

1. Replace Jest-specific functions and mocks with Vitest equivalents
2. Ensure all tests in src/screens/OrgPost pass after migration using npm run test:vitest
3. Maintain the test coverage for the file as 100% after migration
4. Upload a video or photo for this specific file coverage is 100% in the PR description

Additional context

• Refer to the merged PR for the base Vitest configuration:
  https://github.com/PalisadoesFoundation/talawa-admin/pull/2457/files#diff-9a5a35cf8d7f02b2bba90905714b762560579c4789e9eb4cebb4607980aa3d93
• Vitest documentation:
  https://vitest.dev/

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[bandhan-majumder]

Hi @palisadoes . Can I work on this ?

[dhanagopu]

@bandhan-majumder Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[Nirvanjha2004]

@dhanagopu @palisadoes can i work on this issue

[Nirvanjha2004]

update on issue #2566 -

1. completed the migration from jest to vitest
   

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[NishantSinghhhhh]

@palisadoes , Can I work on this issue

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[NishantSinghhhhh]

@Cioppolo14 , Okay after my pr for mockLink gets merged , I will ping you again so that I can be assigned this issue and start working accordingly

[amaan-aly246]

@Cioppolo14 PR for this issue has already been merged. I think you should close this issue.

[Cioppolo14]

@amaan-aly246 Can you post the links so I can verify?

[shivasankaran18]

@palisadoes @Cioppolo14 ..can I work on this issue..?

[Cioppolo14]

@shivasankaran18 Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[maheshxsharmask]

@Cioppolo14 can I work on this issue ?

[shivasankaran18]

@palisadoes @Cioppolo14 ..can I work on this issue..?