Craft Store should raise a better exception if we get an un-decodable response from the server.
Metadata
Current evaluation
No evaluation has been recorded for this issue yet.
Issue body
### Bug Description
It appears that if we get bad text from the store we'll just bubble up a `UnicodeDecodeError` - we should convert that into a `StoreError` of some kind.
### To Reproduce
Not sure if it's reproducible reliably, but here: https://github.com/dell-esg/powerflex-cinder-charm/actions/runs/15607294154/job/43959689846
### part yaml
```shell
```
### Relevant log output
```shell
snap/bin/charmcraft resource-revisions cinder-dell-powerflex sdc-deb-package
charmcraft internal error: UnicodeDecodeError('utf-8', b'\x86\xdbi\xb3\xff\xe0\x8a\xd8nm\xca&\xfd\xd7\xa5\x95\xeb \xfe\x9a0z\xb7\xe5{\x19\xe8\xbd\xa7!j\xb9\xbfi\xcbb\xa2{?\xae\xe9\xec\xff^y\xf3\x9d{\xdb\xad8\xfe:\x1b\xff\x8d\xfc\xf3\xde:\xeb\x8du', 0, 1, 'invalid start byte')
Full execution log: '/home/runner/.local/state/charmcraft/log/charmcraft-20250612-095333.234337.log'
Error: The process '/snap/bin/charmcraft' failed with exit code 70
Error: Error: The process '/snap/bin/charmcraft' failed with exit code 70
at ExecState._setResult (/home/runner/work/_actions/canonical/charming-actions/2.6.2/dist/upload-charm/index.js:3950:25)
at ExecState.CheckComplete (/home/runner/work/_actions/canonical/charming-actions/2.6.2/dist/upload-charm/index.js:3933:18)
at ChildProcess. (/home/runner/work/_actions/canonical/charming-actions/2.6.2/dist/upload-charm/index.js:3827:27)
at ChildProcess.emit (node:events:524:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)
```
Evaluation history
No evaluation history available.