Add unit tests for creator key decimals consistency with token standard

[Chucks1093]

Summary
The creator key decimals method returns a fixed value, but there are no unit tests confirming the value is consistent with the token standard expected by clients and wallets. A unit test that asserts the exact decimals value prevents silent regressions if the value is ever changed.

Scope

• add a unit test that reads the creator key decimals method
• assert the returned value matches the token standard constant
• add a second case that confirms the value is identical across different registered creators

Acceptance Criteria

• the decimals method returns the expected token standard value
• the value is consistent across different creator instances
• the expected value is defined as a named constant in the test

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[Kingvic300]

@Kingvic300 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kingvic300 to this issue.

[numdinkushi]

@numdinkushi has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, let me handle this task

ℹ️ Repo Maintainers: To accept this application, review their application or assign @numdinkushi to this issue.

[khanavi272-spec]

@khanavi272-spec has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @khanavi272-spec to this issue.

[shadrach68]

@shadrach68 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

please assign this issue to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @shadrach68 to this issue.

[drips-wave]

Congratulations, @shadrach68! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @shadrach68: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊