Description

Closes: akash-network/support#619

Scopes the AllProvidersAttributes and AuditorAttributes query pagination to the audit provider key prefix.

Previously both query handlers paginated over the full audit KV store and called ParseIDFromKey for every key. That works while the store only contains provider keys, but it is fragile: any future non-provider key under the same store key could be parsed as a provider ID and cause incorrect results or a panic.

This change wraps the audit store with prefix.NewStore(..., types.PrefixProviderID()) before paginating, so only provider attribute records are scanned. The tests add a non-provider key to the audit store and verify both query paths ignore it.

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed