fix: log warning when bearer token is sanitized

Address review feedback from @Willyfrog: log when sanitizedToken
differs from the original so corrupted tokens are visible in logs
for debugging, without exposing the token value itself.

Co-authored-by: Claude <claude@anthropic.com>

Author: pavelzeman

android/src/main/java/com/mattermost/networkclient/interceptors/BearerTokenInterceptor.kt

@@ -1,5 +1,6 @@
 package com.mattermost.networkclient.interceptors
 
+import android.util.Log
 import com.mattermost.networkclient.ApiClientModuleImpl
 import okhttp3.Interceptor
 import okhttp3.Response
@@ -16,6 +17,9 @@ class BearerTokenInterceptor(private val alias: String, private val bearerAuthTo
             // Corrupted tokens with control characters (e.g. 0x02) cause OkHttp to throw
             // IllegalArgumentException when setting the Authorization header.
             val sanitizedToken = token.replace(Regex("[^\\x20-\\x7E]"), "")
+            if (sanitizedToken != token) {
+                Log.w("BearerTokenInterceptor", "Bearer token contained non-ASCII characters and was sanitized (removed ${token.length - sanitizedToken.length} chars)")
+            }
             if (sanitizedToken.isNotEmpty()) {
                 request = request.newBuilder()
                         .header("Authorization", "Bearer $sanitizedToken")