fix: wrong pico_service password + picodata expel --user

Summary

• fix: used to not provide pico_service password on initial replication configuration
• test: now conftest.Cluster.deploy sets the non-empty pico_service password for the cluster
• fix: picodata expel now accepts --user, --password-file & --auth-method parameters and behaves the same way picodata connect does with respect to credentials

Note that using picodata expel requires providing a user which is authorized to execute stored procedure .proc_expel_redirect. Currently by default the only such user is pico_service and the only way to create another user with such privileges is to go through lua.

---

• Close #...
• Target branch: master
• Changes should be cherry-picked to 24.1: yes / no
• Docs follow-up: docs#199 (closed)

src/cli/admin.rs

@@ -11,7 +11,6 @@ use rustyline::Context;
 use rustyline_derive::{Completer, Helper, Highlighter, Hinter, Validator};
 
 use crate::tarantool_main;
-use crate::util::unwrap_or_terminate;
 
 use super::args;
 use super::connect::ResultSet;
@@ -300,7 +299,10 @@ pub fn main(args: args::Admin) -> ! {
         callback_data: args,
         callback_data_type: args::Admin,
         callback_body: {
-            unwrap_or_terminate(admin_repl(args));
+            if let Err(e) = admin_repl(args) {
+                crate::tlog!(Critical, "{e}");
+                std::process::exit(1);
+            }
             std::process::exit(0)
         }
     );