Runtime panic on faucet call

[gztensor]

No matter if pow-faucet feature is used or not, the runtime panics when btcli is used to run faucet.

Steps to reproduce:

1. Checkout dynamic branch in subtensor
2. Run the local network with ./scripts/localnet.sh. Optionally, the pow-faucet feature may be disabled.
3. Execute btcli to use faucet:

btcli w faucet --subtensor.network ws://127.0.0.1:9946

4. Observe panic in subtensor logs:

====================

Version: 5.0.0-2bf029a05cd

   0: backtrace::capture::Backtrace::new
   1: sp_panic_handler::set::{{closure}}
   2: std::panicking::rust_panic_with_hook
   3: std::panicking::begin_panic_handler::{{closure}}
   4: std::sys_common::backtrace::__rust_end_short_backtrace
   5: _rust_begin_unwind
   6: core::panicking::panic_fmt
   7: node_subtensor_runtime::api::dispatch
   8: environmental::using
   9: sc_executor::executor::WasmExecutor<H>::with_instance::{{closure}}
  10: sc_executor::wasm_runtime::RuntimeCache::with_instance
  11: <sc_executor::executor::NativeElseWasmExecutor<D> as sp_core::traits::CodeExecutor>::call
  12: sp_state_machine::execution::StateMachine<B,H,Exec>::execute
  13: <sc_service::client::call_executor::LocalCallExecutor<Block,B,E> as sc_client_api::call_executor::CallExecutor<Block>>::contextual_call
  14: <sc_service::client::client::Client<B,E,Block,RA> as sp_api::CallApiAt<Block>>::call_api_at
  15: <node_subtensor_runtime::RuntimeApiImpl<__SrApiBlock__,RuntimeApiImplCall> as sp_consensus_aura::AuraApi<__SrApiBlock__,sp_consensus_aura::sr25519::app_sr25519::Public>>::__runtime_api_internal_call_api_at
  16: sp_transaction_pool::runtime_api::TaggedTransactionQueue::validate_transaction
  17: tracing::span::Span::in_scope
  18: sc_transaction_pool::api::validate_transaction_blocking
  19: <sc_transaction_pool::api::FullChainApi<Client,Block> as sc_transaction_pool::graph::pool::ChainApi>::validate_transaction::{{closure}}::{{closure}}
  20: sc_transaction_pool::api::spawn_validation_pool_task::{{closure}}
  21: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
  22: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
  23: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
  24: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
  25: tokio::runtime::park::CachedParkThread::block_on
  26: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  27: tokio::runtime::task::core::Core<T,S>::poll
  28: tokio::runtime::task::harness::Harness<T,S>::poll
  29: tokio::runtime::blocking::pool::Inner::run
  30: std::sys_common::backtrace::__rust_begin_short_backtrace
  31: core::ops::function::FnOnce::call_once{{vtable.shim}}
  32: std::sys::pal::unix::thread::Thread::new::thread_start
  33: __pthread_joiner_wake


Thread 'tokio-runtime-worker' panicked at 'Bad input data provided to validate_transaction: Could not decode `ChargeTransactionPayment.0`:
out of range decoding Compact<u64>
', runtime/src/lib.rs:1255

This is a bug. Please report it at:

	support.anonymous.an