SAMBA 3 support missing

Describe the bug
Hello! Congrats for the amaz-ing work done on this project!
Before opening this issue I have searched and I find out #1225 -> #670 -> #1633 but seems that only Samba v2 has been implemented.

I'm updating my personal SAMBA instance and during regression test, I have find out that Amaze is not able to connect at SAMBA v3+, only till v2

To Reproduce

1. Use whatever SAMBA config you want
2. In [global] set log level at 3 (maybe lower, but higher than 2): log level = 3 and logging = systemd@3 to be able to run sudo journalctl -u smbd -f in terminal and see logs
3. In [global] go for the higher protocol v2 ( it is SMB2_10 based on documentation ) : server min protocol = SMB2_10
4. Amaze connects to Samba
5. upgrade to the first available v3: server min protocol = SMB3_00
6. Amaze will not connect to Samba
7. From sudo journalctl -u smbd -f it appears:

Selected protocol SMB 2.???
source3/smbd/smb2_server.c:4074(smbd_smb2_request_error_ex)
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NOT_SUPPORTED] || at source3/smbd/smb2_negprot.c:288

Expected behavior
Amaze gets connected to SAMBA with setup at v2 or v3; other applications on same phone does it (just to be sure it is allowed from the system/age of the system)

Smartphone (please complete the following information):

• Device: Moto G62
• OS: Android 13
• Rooted: No
• Version: 3.11.2

No source file or test is named. Reproduce the connection using the reported SMB2_10 and SMB3_00 configurations, then trace the Android app's SMB connection and protocol-negotiation entry point using the Samba journal output. Done means Amaze connects to both Samba v2 and v3+ configurations on the reported device and Android version.