feat(platform): add store app enablements command

[tmittal-godaddy]

Summary

JIRA - https://godaddy-corp.atlassian.net/browse/DEVX-1075

Adds gddy platform app enablements --store-id <storeId> — the read counterpart to enable / disable — so you can verify which developer-platform apps are bound to a commerce store.

• Calls enabledStoreApplications(storeId) with GraphQL variables only (APP_REGISTRY_READ)
• Empty list is success ([]), not an error - means if given storeId has no apps enabled, the command still exits successfully and prints []
• Defaults: name,status,releaseVersion (flattens API release.version)
• Opt-in via --fields: id, label (or --fields all)
• Wires enable / disable next_actions + help/docs to point at enablements

Behavior

Situation	Result
Store has enabled apps	Success + list of apps
Store has zero enabled apps	Success + [] (not an error)
Store you can’t access / bad store id	Error (UNAUTHORIZED)

Usage

# List apps enabled on a store (defaults: name, status, releaseVersion)
gddy platform app enablements --store-id <storeId>

# Include id and/or label
gddy platform app enablements --store-id <storeId> --fields id,label,name,status,releaseVersion
gddy platform app enablements --store-id <storeId> --fields all

# JSON output
gddy platform app enablements --store-id <storeId> --output json

# Typical verify flow
gddy platform app enable <name> --store-id <storeId>
gddy platform app enablements --store-id <storeId>
gddy platform app disable <name> --store-id <storeId>
gddy platform app enablements --store-id <storeId>

Notes

• list / info = developer App Registry catalog; enablements = per-store bindings
• Store you cannot access → GraphQL UNAUTHORIZED (not [])
• Presence in the list means enabled; status is registry lifecycle (usually ACTIVE)

Example output shape

[
  {
    "id": "app-1",
    "name": "my-app",
    "label": "My App",
    "status": "ACTIVE",
    "releaseVersion": "1.0.0"
  }
]

Test plan

• cargo test --workspace enablements (7 passed)
• cargo test --workspace list_enabled_store (2 passed)
• Manual smoke on test env: enable → enablements → disable → enablements

[smukherjee-godaddy]

CI follow-up: the cicd check is failing at cargo fmt --check in rust/src/application/commands/enablements.rs (the flatten_enablements_null_release_version_when_missing assertion around line 165). Compilation completed successfully; the formatting diff is the blocker. Please run cd rust && cargo fmt, commit the formatting change, and push it so CI can rerun.