fix: file upload 403 no longer clears token or triggers logout

403 from the file service (e.g. permissions/CORS error) was incorrectly
treated as an auth failure, removing the token and redirecting to login.
403 should only show an error message; only 401 indicates an auth failure.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

tenant-platform/src/api/file.ts

@@ -55,11 +55,7 @@ fileClient.interceptors.response.use(
       return Promise.reject(error)
     }
     if (status === 403) {
-      localStorage.removeItem('token')
-      if (router.currentRoute.value.path !== '/login') {
-        router.push('/login?reason=' + encodeURIComponent('登录已失效，请重新登录'))
-      }
-      ElMessage.error(error.response?.data?.message ?? '登录已失效，请重新登录')
+      ElMessage.error(error.response?.data?.message ?? '无权限执行此操作')
       return Promise.reject(error)
     }
     const msg = error.response?.data?.message ?? '文件请求失败'