[FIX] regex not allowed for cors_origins

Steps to reproduce:
Adding origins such as chrome-extension://{id} or moz-extension://{id}
through the UI causes the server to crash at startup without any explanation.

When trying to start the server manually, an error is displayed
```
[ERROR][panic]: thread 'main' panicked at 'Failed to set up CORS:
OpaqueAllowedOrigin(["chrome-extension://{any_id}"])':
aw-server/src/endpoints/cors.rs:69
```

Source:
This happens because these schemes are not valid for allowed_exact_origins
and are treated as opaque origins by the CORS layer.

The server currently allows any string to be inserted into:
allowed_exact_origins (via cors)
allowed_regex_origins (via cors_regex)

However, non-HTTP schemes (chrome-extension://, moz-extension://, etc.) are invalid
in allowed_exact_origins and cause a panic when initializing CORS.

Solution:
Short term Solution: Validate origins before inserting them into allowed_exact_origins to accept only
http:// and https://
Other Solutions:
1- add a regex_cors field
2- accept regex for browser extensions and put the automatically in allowed_regex_origins

Author: RaoufGhrissi

aw-client-rust/.gitignore

@@ -8,3 +8,5 @@ Cargo.lock
 
 # These are backup files generated by rustfmt
 **/*.rs.bk
+
+.vscode

aw-server/src/endpoints/cors.rs

@@ -21,9 +21,7 @@ pub fn cors(config: &AWConfig, datastore_mutex: &Mutex<Datastore>) -> rocket_cor
             .filter(|s| !s.is_empty())
             .filter(|s| {
             let is_valid = s.starts_with("http://")
-                        || s.starts_with("https://")
-                        || s.starts_with("chrome-extension://")
-                        || s.starts_with("moz-extension://");
+                        || s.starts_with("https://");
             if !is_valid {
                 log::warn!("Ignoring invalid CORS origin: '{}'", s);
             }