fix: hb_store_gateway:remote_hyperbeam_node_ans104_test flaky test

[speeddragon]

Running the following test command can generate a flaky test when in the list of commitments, the order is different from ans104, httpsig.

HB_PRINT=hb_gateway_client,dev_query_graphql,http_client_short,http_server_short,warning rebar3 eunit --test hb_store_gateway:remote_hyperbeam_node_ans104_test

Since we match on the first commitment of the list, if httpsig is the first item will return the HMAC signature.

HyperBEAM/src/ar_bundles.erl

Line 139 in 77b398f

hb_util:ok_or_throw(TX,

will throw because the signature will be 32 bytes (eDAf0cyPL8svRojdP8HyCaBpvxG5ae_33xM3gfLRw9k) and not a valid ar_bundles signature.

I've applied the same logic of the owner field below, to ensure that we select the commitment with a commiter (httpsig commitment doesn't have commiter field).