Node Wizard Update and Cloud Account

Adding node wizard update: - Wizard - modal window, should not disappear if you clicks away. Cancel button must always be available - Disregard mobile optimization. The primary is Web. Mobile should be functional but not primary. - 1\. How - change to bullets - user can pick any, more info shows up with details. Then user clicks next - Host with Jaah page - change from buttons to bullets - Use my cloud account: - Connection: drop down with the list of connections + Add new - Instance type - If instance fails to start - show exact error from AWS Adding Connection (refactored launch defaults): - Name: - Provider: AWS / GCP / Azure. GCP and Azure are grayed out - Credentials: list of compatible creds + Add new - Advanced: optional fields that are now in aws launch defaults. Only AWS is supported now. From most common: region (lookup dropdown), subnet (lookup dropdown), security group (lookup dropdown), Root volume (default 50), Description. Remove Instance profile, Join the tailnet (always yes), Associate public IP (always no). EFS settings only visible to Operator for now. Show sketches of each page before building.

Node wizard (true modal, radio lists, renamed ways, connection picker + Add new, AWS error verbatim) and cloud connections (many per credential, lookups, inline credential, EFS operator-only) merged via PR #4800; full gate green; Jaah Deploy succeeded. Review-lane findings fixed; visual check done on the live stack (Jaah Cloud page unit-tested only: no local hosting capacity). Rejected: operator filing a tenant's credential from the wizard. mem-674 proposed.