Not to add insult to injury, but the initial switch to edge was probably in the wrong direction. That should have been the moment to snap revert on a production system. There is also a less permanent way of installing only a singular version from another channel without actually switching to it, which I use whenever I am impatient and want to get the latest major release of Firefox, without having to wait for the QA cooldown.
sudo snap refresh --revision=<revid>
And, since the FF snap can’t be updated while it’s running, most of the time at least – there seem to be exceptions – I can just leave it running. Once that revision trickles down into the stable channel, only the snap info part pertaining to the channels changes.
Or I could just hold refreshes for that particular package:
snap refresh --hold firefox --revision=<revid>
That can be required to prevent snapd from downgrading to the stable channel version, which has happened to me, while Firefox was running; I only noticed because I actually did restart it and was warned that opening a user profile touched by a newer version of FF was dangerous. That may have been an instance of said exceptions, because usually snap refresh firefox is blocked by the running instance. Or it was just snapd doing a switcheroo to the already installed older revision, because it matched the tracked channel? Anyhow, I only want to illustrate what can happen when doing such things; take whatever you want from the Firefox example.