fix: lookup of resolved provider

[bajtos]

• Look up inactive and unapproved SPs, as FilBeam includes such SPs in the list of retrieval options

• Fix deserialisation of capability values - RPC API returns them as hex-encoded string starting with 0x, not as a Buffer instance.

• Rework the code building the "resolved as" part of the alert message to include more details about the resolved SP

Example output:

dataSetId=50 from unapproved active SP providerId=6 serviceUrl=http://pdp.660688.xyz:8880
dataSetId=100 from approved active SP providerId=4 serviceUrl=https://caliberation-pdp.infrafolio.com
dataSetId=150 from approved active SP providerId=2 serviceUrl=https://calib2.ezpdpz.net
dataSetId=155 from unapproved active SP providerId=14 serviceUrl=http://116.182.28.4:12310
<data set not reported>
<invalid data set ID NaN>

My intention is to improve the following alert seen recently in Slack - notice that there is no information about the SP:

Nov 7, 2025 08:29:08 2603 vector ALERT Cannot retrieve data set 39 piece 183 
(resolved as data set 155 from SP <unknown>) 
from fra via https://0xa27774ac5edfb083805cd4e8d9aa35b89648bc79.calibration.filbeam.io/bafkzcibetxqqmdji4h34ptultrnokrfbnown3l4wcon4geigzomf54dsxldkvwusfi: 
403 error code: 1003

[juliangruber]

Surprising, but if it works it works 👍