fix: route collab error map messages to appropriate console levels

[kptdobe]

Summary

• 401 messages → console.warn (auth info, not an error)
• 403 messages → console.log (permission info, not an error)
• All other messages → console.error with errorMap.toJSON() payload for full context
• Message is read from errorMap.get('message'), falling back to JSON.stringify(errorMap.toJSON()) when no message key is set

This aligns with adobe/da-collab#157 - no need for an ugly error message in case of an expired token (403). 401 is more unexpected (some removed author full access to the file ?) but still warning is enough.

If message received is 403: sign up popup appears. If author signs in, latest changes are even restored and persisted
If message received is 401: redirected to the 404 page.

Test plan

• Routes 401 messages to console.warn — verifies warn path and message prefix
• Routes 403 messages to console.log — verifies log path and message prefix
• Routes other messages to console.error with toJSON payload — verifies error path + payload
• Clears the error map after logging — verifies errorMap.clear() is always called
• Falls back to JSON when no message key is set — verifies fallback serialisation

🤖 Generated with Claude Code

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• 20beee0 ✅ (latest)