double submit issue resolved

[GarvitSinghal47]

Fixes #4144

Summary

Description of the change(s) you made

I've added a new state mechanism to prevent concurrent save operations. Previously, multiple clicks on the save button could trigger simultaneous saves, leading to potential issues.

Changes Made:
Added a saving state to prevent multiple save operations.

Purpose:
This ensures that a save/submit operation must complete before another one can be initiated, preventing unintended side effects.

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

[LianaHarris360]

Hi @GarvitSinghal47 thank you for working on this. The failing JavaScript Linting test will need to be fixed before this pr can be approved and merged. You can manually run the auto-formatters with yarn run lint-frontend:format, or install pre-commit hooks to automatically have this done when you commit changes, more about this can be found in the Kolibri developer documentation.

Also, if you include a brief description of the changes you made and any instructions on how we can test those changes, that would assist us in reviewing your PR quicker.

[LianaHarris360]

The changes look great and correctly fix the accidental creation of multiple channel collections. Thank you!