state: Gas *price* should be estimated using the estimator service

[renaynay]

In #4168, gas price estimation was implemented only for transactions that are not MsgPayForBlob due to a misunderstanding of the ADR.

We need to change the gas price estimation for blob submission in state/core_access.go to, instead of just querying for the minimum gas price, to actually use the estimator service to query gas price as well

[renaynay]

cc @jcstein @cmwaters

[jcstein]

We need to change the gas price estimation for blob submission in state/core_access.go to, instead of just querying for the minimum gas price, to actually use the estimator service to query gas price as well

should this also check against max.gas.price to ensure the gas price that is estimated is not greater than what the user has set? i.e. transactions 2-4 below should all have failed

celestia blob submit 676d 676d --max.gas.price 0.002
{
  "result": {
    "height": 5333544,
    "commitments": [
      "0xb4774f791439fb1c09ee293812bf7dc7cfc75f20c49dd16d061459dc8f5febff"
    ]
  }
}
celestia blob submit 676d 676d --max.gas.price 0.001
{
  "result": {
    "height": 5333545,
    "commitments": [
      "0xb4774f791439fb1c09ee293812bf7dc7cfc75f20c49dd16d061459dc8f5febff"
    ]
  }
}
celestia state account-address
{
  "result": "celestia1glsg9w0p6d9qw6vv79xd0w6vav7sret9stpxuy"
}
celestia blob submit 676d 676d --max.gas.price 0.0001
{
  "result": {
    "height": 5333566,
    "commitments": [
      "0xb4774f791439fb1c09ee293812bf7dc7cfc75f20c49dd16d061459dc8f5febff"
    ]
  }
}
celestia blob submit 676d 676d --max.gas.price 0.0000001
{
  "result": {
    "height": 5333569,
    "commitments": [
      "0xb4774f791439fb1c09ee293812bf7dc7cfc75f20c49dd16d061459dc8f5febff"
    ]
  }
}

these all have the same fee... (1, 2, 3, 4 on celenium) AFAIU the 0.001, 0.0001 and 0.000001 should all have failed

AFAIU the issue I hit was that the gas price limit was set very low, and although the actual gas price was higher than this, it still let the transaction go through.