Drop `components::` from component NAME constants

[partylikeits1983]

Summary

Several auth components in miden-standards declare a NAME constant under miden::standards::components::auth::*, even though the storage slots they own live at miden::standards::auth::*. As Bobbin pointed out in PR #2817, the component name should be a prefix of the storage-slot names contained within it, so that off-chain tooling can match a slot to its owning component by string prefix.

PR #2817 already does this for AuthNetworkAccount (renaming miden::standards::components::auth::network_account to miden::standards::auth::network_account). Bobbin asked that the same change be made for the remaining auth components, but not in that PR, hence this follow-up.

Affected NAME constants

Component	File	Current NAME
NoAuth	crates/miden-standards/src/account/auth/no_auth.rs	miden::standards::components::auth::no_auth
SingleSig	crates/miden-standards/src/account/auth/singlesig.rs	miden::standards::components::auth::singlesig
SingleSigAcl	crates/miden-standards/src/account/auth/singlesig_acl.rs	miden::standards::components::auth::singlesig_acl
Multisig	crates/miden-standards/src/account/auth/multisig/mod.rs	miden::standards::components::auth::multisig
GuardedMultisig	crates/miden-standards/src/account/auth/guarded_multisig.rs	miden::standards::components::auth::guarded_multisig

For each, drop the components:: segment so e.g. SingleSig::NAME becomes miden::standards::auth::singlesig.

Notes

• Pure string rename: storage layout is unchanged, the on-chain account representation is unchanged.
• NAME is consumed via Self::NAME inside each component's component_metadata(). Search for any external consumer that compares the literal string before changing.
• Coordinate with downstream tooling (e.g. account inspectors / explorers) if any of them prefix-match the literal.

References

• PR feat(standards): add NetworkAccount auth component #2817 (AuthNetworkAccount is the first component migrated).
• Bobbin's review comment requesting the broader cleanup: feat(standards): add NetworkAccount auth component #2817 (comment)

[bobbinth]

This is also related to #2854 - though extends this beyond just auth components.

[AlgofootPrint]

I'd like to take this on! I've noted Bobbin's comment linking to #2854 since that one is currently blocked by the path collision in build.rs, I'll scope this PR strictly to the five auth component NAME constants as described here, following the same pattern from PR #2817:

• NoAuth: miden::standards::components::auth::no_auth →
  miden::standards::auth::no_auth
• SingleSig: miden::standards::components::auth::singlesig →
  miden::standards::auth::singlesig
• SingleSigAcl: miden::standards::components::auth::singlesig_acl →
  miden::standards::auth::singlesig_acl
• Multisig: miden::standards::components::auth::multisig →
  miden::standards::auth::multisig
• GuardedMultisig:
  miden::standards::components::auth::guarded_multisig →
  miden::standards::auth::guarded_multisig

I'll also check for any external consumers of these literal strings before changing. PR will target next. Could someone assign this to me?

[bobbinth]

I've expanded the scope of this to cover all components.