Fixed Inconsistent Use of Icons to Minimize Left Column Navbar in Event Management Screen

[akhilender-bongirwar]

What kind of change does this PR introduce?

• Implemented the same minimization method used in the main organization pages, ensuring a consistent user experience throughout the application.

Issue Number:

Fixes #1240

Did you add tests for your changes?
Yes

Snapshots/Videos:

2024-01-07.23-45-07.mp4

If relevant, did you update the documentation?
No

Summary
Now there is consistency in minimization of the left column navbar in event mangement screen.

Does this PR introduce a breaking change?
No

Other information

Have you read the contributing guide?

Yes

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (628b3f5) 97.44% compared to head (5fff5b5) 97.45%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1403   +/-   ##
========================================
  Coverage    97.44%   97.45%           
========================================
  Files          138      138           
  Lines         3683     3690    +7     
  Branches      1076     1079    +3     
========================================
+ Hits          3589     3596    +7     
  Misses          89       89           
  Partials         5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[EshaanAgg]

LGTM

[palisadoes]

The intention was for there to be a single way to expand and retract the left drawer. We still have two ways which is not intuitive.

1. The expectation that this would be the sole methodology of expanding the drawer
   
2. And that this way would be the only way to retract it.
   

In all cases on this screen

[akhilender-bongirwar]

@palisadoes according to the solution stated in the issue, I have implemented the same method for opening and closing the sidebar as used in the remaining main organization pages to maintain consistency throughout the application. Please check the video below.

2024-01-09.14-31-08.mp4

[palisadoes]

We'll need to open another issue specifically for the modification for consistency