fix: Reorder and rename event dashboard boxes

[Soumi150]

Fixes #5468

Short description of what this resolves:

Reorder and rename event dashboard boxes.

Checklist

• I have read the Contribution & Best practices Guide.
• My branch is up-to-date with the Upstream development branch.
• The acceptance, integration, unit tests and linter pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Before

After making changes

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/c61p4t344
✅ Preview: https://open-event-frontend-git-change1.eventyay.vercel.app

[iamareebjamal]

Before and after screenshots

[codecov]

Codecov Report

Merging #5471 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #5471   +/-   ##
============================================
  Coverage        23.24%   23.24%           
============================================
  Files              493      493           
  Lines             5170     5170           
  Branches            38       38           
============================================
  Hits              1202     1202           
  Misses            3963     3963           
  Partials             5        5           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 025080d...71ed082. Read the comment docs.

[iamareebjamal]

And please resolve the conflicts

[Raunaksingh100]

@Soumi150 if someone do comment i am working on this so first ask that he is not working on it so can i work on it

(It lead to duplicate work)

plz follow the codeheat rules and community rules

[iamareebjamal]

If @carrycooldude has a PR, we'll close this one. But we value actual contribution. Not just commenting "I want to work on this" and then disappearing on a trip to Bahamas. We will not stop other contributors from contributing just because someone commented "I want to work on this" or "I am working on this"

If they have commented and started the work, they can send a PR, even an incomplete one as a proof and ask this PR to be closed. We'll do it without any problem. But it's in fashion these days to just say I want to work on this issue and then forget about it. Actual contributions are hurt because of this and this is bad for both the contributors who could fix the issue and get codeheat rewards and also for us because the issue doesn't get solved.

For example, you can't just reserve a Phone from amazon and say "I'll pay for it" and prevent others from buying it. If you don't finalize payment within 2-3 hours, it'll be sold to someone else. We usually allow up to 7 days. But if someone else can immediately start working on something within hours and you haven't started working on it, the issue should go to that person.

That's why please only comment on an issue you actually will be fixing and soon, otherwise anyone else who can send a PR soon will get that. And it is only fair