MS-1513 Add another log archive password fallback when project ID not available

[luhmirin-s]

JIRA ticket
Will be released in: 2027.1.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.1.0

• Creating log archive requires a non-blank password string.
• We used either settings password from config or project ID.
• Before logging in both are not available.

Notable changes

• Added another fallback to device ID in for pre-login extraction.
• IMO, it is fairly safe to use device ID since before login logs do not have any project details.

Testing guidance

• Open SID without authentication.
• Press 5 times on the logo.
• Extract logs.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[Copilot]

🟡 Changes recommended

Add test coverage for whitespace-only settings passwords and project IDs falling back to the device ID.

1 open issue

• Add coverage for whitespace-only password and project ID fallbacks · New

What changed in this PR

Adds a device ID fallback for log archive passwords when settings and project ID are unavailable, enabling pre-login log extraction.

Changes:

• Selects the first non-blank value from settings password, project ID, or device ID.
• Adds archive password and fallback coverage tests.

File	Summary
feature/​troubleshooting/​src/​test/​java/​com/​simprints/​feature/​troubleshooting/​overview/​usecase/​ExportLogsUseCaseTest.kt	Verifies archive creation and fallback passwords.
feature/​troubleshooting/​src/​main/​java/​com/​simprints/​feature/​troubleshooting/​overview/​usecase/​ExportLogsUseCase.kt	Implements non-blank password fallback logic.

_{Review effort: Lite}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud