fix: resolve authentication persistence issues

[komplexb]

Summary

• Fix authentication persistence issues causing repeated device login prompts in Lambda environment
• Implement proper MSAL authentication patterns using acquireTokenSilent() instead of manual refresh token handling
• Resolve path resolution issues in webpack bundled serverless environment
• NEW: Enhance cache persistence with comprehensive error handling and backup mechanisms
• NEW: Add detailed logging for authentication flow debugging and troubleshooting
• NEW: Implement manual cache persistence to ensure tokens are always saved to DynamoDB

Key Improvements in Latest Commit

• Enhanced Cache Plugin: Added comprehensive error handling, logging, and path resolution improvements
• Manual Cache Persistence: Added persistCache() function as backup mechanism called after successful operations
• Token Validation: Improved token expiry validation with proper extended expiry time usage and buffer calculations
• Debugging: Added detailed logging throughout authentication flow for better troubleshooting
• Error Recovery: Enhanced device login fallback with guaranteed cache persistence

Technical Details

• Cache persistence now has dual mechanisms: MSAL plugin + manual backup
• Token validation uses extExpiresOn with 5-minute buffer for extended validity
• Comprehensive logging added for cache loading, persistence, and token validation
• Error handling improved for file operations and DynamoDB persistence
• Path resolution enhanced for webpack bundling context

Test plan

• Deploy to dev environment and verify tokens persist across Lambda invocations
• Test device login fallback still works when tokens are invalid
• Verify comprehensive logging provides debugging information
• Confirm admin notifications are sent for authentication failures
• Verify no repeated login prompts during normal operation (testing in progress)

🤖 Generated with Claude Code