Tested verification process more. Cleaned up and tweaked verification UI

Everything works beautifully now and is ready for merge.

Post-merge, there are some improvements we can make:
* If we're transitioning from an unverified/unknown device state
  to a verififed state, then we need to do two things for rooms
  that are E2EE:
  1. Re-request/re-render all of the latest messages
  2. Clear the drawn cache in those timelines.

Author: kevinaboos

Cargo.lock

@@ -17,7 +17,7 @@ metadata.makepad-auto-version = "zqpv-Yj-K7WNVK2I8h5Okhho46Q="
 
 [dependencies]
 # makepad-widgets = { git = "https://github.com/makepad/makepad", branch = "rik" }
-makepad-widgets = { path = "../makepad/widgets" }
+makepad-widgets = { git = "https://github.com/kevinaboos/makepad", branch = "modal_sends_dismissed_action_to_inner_modal_content" }
 
 ## Including this crate automatically configures all `robius-*` crates to work with Makepad.
 robius-use-makepad = "0.1.0"

Cargo.toml

@@ -170,8 +170,10 @@ async fn sas_verification_handler(
             }
             SasState::Cancelled(cancel_info) => {
                 log!("SAS verification has been cancelled, reason: {}", cancel_info.reason());
-                // No need to send a specific action here, the VerificationRequestState stream loop 
-                // will handle the Cancelled state and send a RequestCancelled action.
+                // We go ahead and send the RequestCancelled action here,
+                // because it is not guaranteed that the VerificationRequestState stream loop 
+                // will receive an update an enter the `Cancelled` state.
+                Cx::post_action(VerificationAction::RequestCancelled(cancel_info));
                 break;
             }
         }