admin-panel collection error resolved

[GarvitSinghal47]

Fixes : #4145

Summary

Description:
In the current setup, the frontend was fetching and displaying all channels without properly handling the edit flag or checking if the channels were associated with the current user_id. This inconsistency led to sporadic issues where channels would sometimes show up in the admin list and sometimes not.

Changes Made:

Modified the frontend logic to only fetch and display channels where edit is set to true or the user_id matches the current user.
Ensured proper handling to prevent channels from being displayed inconsistently in the admin list.

Manual verification steps performed

1. Step 1
2. Step 2
3. ...

Screenshots (if applicable)

Does this introduce any tech-debt items?

---

Reviewer guidance

How can a reviewer test these changes?

Are there any risky areas that deserve extra testing?

References

Comments

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[ozer550]

After having a quick conversation with @bjester, We have decided to go forward with the prior way of creating the queryset i.e we don't want to do it all in one go, apologies for this @GarvitSinghal47! One thing to note here is your earlier commit was filtering first and then doing the annotation to the queryset which could become problematic. The right way would be to first annotate and then to filter with edit=True.

[ozer550]

LGTM!