Creating useSnackbar composable and replacing existing logic with it

[nathanaelg16]

Summary

This change creates a new useSnackbar composable and migrates existing logic to use it.

References

• Fixes Create composable for snackbar state and replace existing logic with it #12206

Testing checklist

• 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
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• 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

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.17.0a0.dev0_git.171.g928db739.pex
Windows Installer (EXE)	kolibri-0.17.0a0.dev0+git.171.g928db739-windows-setup-unsigned.exe
Debian Package	kolibri_0.17.0a0.dev0+git.171.g928db739-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.17.0a0.dev0+git.171.g928db739.dmg
Android Package (APK)	kolibri-0.17.0a0.dev0+git.171.g928db739-0.1.4-debug.apk
TAR file	kolibri-0.17.0a0.dev0+git.171.g928db739.tar.gz
WHL file	kolibri-0.17.0a0.dev0+git.171.g928db739-py2.py3-none-any.whl

[nucleogenesis]

Thank you for this @nathanaelg16 -- I'm going to give this a closer look early next week and test it out and I'm looking forward to it :)

[rtibbles]

I have taken a first look at this, and nothing raised any concerns.

We just merged a PR up from release-v0.17.x which has caused a merge conflict, so if you could rebase and fix that, that would be great!

[rtibbles]

This all seems correct, and very straight forward! I'll do a quick manual test to ensure there's nothing concerning here, but I don't see any reasons to think so from the code.

[rtibbles]

A quick manual QA of several affected places shows no regressions. This is good to go!

[rtibbles]

Excellent work again, @nathanaelg16 - this is very thorough and systematic!