Add test for unsupported currency code handling in currency normalization

[Inkman007]

Description:
utils/currency_normalization.py converts trade amounts between asset denominations. The behavior when an unrecognised or malformed currency/asset code is passed in isn't covered by tests/test_currency_normalization.py. Contributors extending the normalizer to support new assets need a clear, tested contract for what happens on invalid input (raise, or pass through unchanged with a logged warning).

Acceptance Criteria:

• A new test case in tests/test_currency_normalization.py passes an unsupported/garbage currency code.
• The test documents and asserts the actual expected behavior (exception type and message, or fallback value).
• If no defined behavior exists yet, add one (a specific exception class) and document it in a short docstring.
• make test passes.

Relevant files:
utils/currency_normalization.py, tests/test_currency_normalization.py

[Ranjeet2063]

Hi everyone,

I would like to resolve this issue. Here is my proposed execution plan for Add test for unsupported currency code handling in currency normalization:

• Implementation: Implement Add test for unsupported currency code handling in currency normalization with explicit require_auth checks, clean storage schemas, and robust Soroban contract logic.
• Testing & Verification: Add unit tests asserting both happy-path invocations and unauthorized revert conditions.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

Excited to work on this—please assign to me and I'll submit a clean PR shortly!

[shobhamerabacha-star]

Hello! I'd like to work on this issue.

I can tackle Add test for unsupported currency code handling in currency normalization. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Ledger-Lenz/Ledgerlens-data
• Implementation: Implement Add test for unsupported currency code handling in currency normalization with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.
• PR: Atomic commit with clean git hygiene and passing CI

I am ready to start immediately—please assign this to me!