`missing-zero-address-check`'s `SENSITIVE_NAMES` requires an exact function-name match — no prefix/substring matching

[unrealtim-tech]

Labels: enhancement, checks-crate, good first issue
Crate: checks

Description
crates/checks/src/zero_address.rs (lines ~16-25, ~106-109) matches sensitive function names with SENSITIVE_NAMES.contains(&fn_name.as_str()) — an exact string match against a fixed list (set_owner, set_admin, initialize, init, transfer_ownership, update_admin, set_manager, set_operator). Common real-world variants like set_owner_v2, initialize_admin, try_set_admin, or set_operator_address never match and are silently skipped, even when they accept an unguarded Address and write it to storage.

Closed issue #30 already established prefix-matching precedent for the (different) admin-detection check; this check never received the equivalent treatment.

Acceptance Criteria

• Match function names by prefix/substring against SENSITIVE_NAMES (or otherwise fuzzy-match), consistent with unprotected-admin's approach.
• Add tests for at least one prefixed/suffixed variant of a sensitive name.

Difficulty: beginner

[Ebby46]

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

Hello, pls i will like to work on this issue

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

[Tobi-8]

@Tobi-8 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

please maintainer , assign me to this issue. I have looked through your description, and i have had experience in this type of issue.
kindly assign

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