Add helper for sanitizing creator bio content before indexing

[Chucks1093]

Summary
Creator bio content submitted by users may contain HTML tags, invisible Unicode characters, or excessive whitespace that should be stripped before the bio is stored and indexed. A sanitization helper applied at the write path ensures stored bios are clean.

Scope

• add a helper that strips HTML tags, invisible Unicode, and normalizes whitespace in a bio string
• apply the helper in the creator registration and profile update paths
• add a unit test covering HTML injection, zero-width characters, and multi-space inputs

Acceptance Criteria

• HTML tags are stripped from stored bio content
• invisible Unicode characters are removed
• whitespace is normalized to single spaces

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

[victor62-art]

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

pls assign this issue to me

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

[SamixYasuke]

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

Hi maintainer, I’d add a reusable bio sanitization helper that removes HTML tags, strips invisible Unicode characters, and normalizes excessive whitespace before content is stored. I’d integrate it into both creator registration and profile update flows, and add unit tests covering HTML injection, zero-width characters, and whitespace normalization to ensure indexed bios remain clean and consistent.

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

[wavyboy-build]

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

Dear maintainer, pls assign me this issue

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

[Benedict315]

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

Hello I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Benedict315 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.

[drips-wave]

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

🧑‍💻 @victor62-art: 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 🌊