Revise Arabic error messages in localization file

[nazem0]

Updated Arabic localization messages for error handling.

Description

Improved Arabic localization messages to make them more natural, user-friendly, and consistent across the application.

Changes include:

• Replaced literal or awkward translations with more natural Arabic phrasing
• Unified tone and terminology across error messages
• Improved authentication and authorization messages
• Refined session expiration and validation texts
• Enhanced overall UX readability for Arabic-speaking users

This change is not breaking.

Checklist

• I fully tested it as developer / designer and created unit / integration tests
• I documented it (or no need to document or I will create a separate documentation issue)

How to test it?

• Switch the application language to Arabic
• Trigger different error scenarios (401, 403, 404, validation, server errors, session expiration)
• Verify that messages appear naturally in Arabic and are consistent with the English localization

[CLAassistant]

All committers have signed the CLA.

[nazem0]

@gterdem

[Copilot]

Pull request overview

Updates the Arabic (ar) localization strings for the ExceptionHandling module to improve readability and consistency of user-facing error messages.

Changes:

• Refined phrasing for common server/validation/default error messages.
• Updated authentication/authorization (401/403) and not-found (404) message wording.
• Adjusted additional messages such as concurrency, authorizing, invalid token, and session expiration.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[maliming]

Thanks @nazem0 👍