Flaky test: recovery::gas_price_updater__can_recover_on_startup_when_gas_price_db_is_ahead

[netrome]

Observed in CI: https://github.com/FuelLabs/fuel-core/actions/runs/11580859867/job/32240358008?pr=2396

Run cargo test --workspace
   Compiling fuel-core-types v0.40.0 (/home/runner/actions-runner/_work/fuel-core/fuel-core/crates/types)
   Compiling fuel-core-metrics v0.40.0 (/home/runner/actions-runner/_work/fuel-core/fuel-core/crates/metrics)
...

test vm_storage::tests::read_sequential_range::read_subset_of_partially_set_range_without_running_too_far ... ok
test vm_storage::tests::read_sequential_range::read_uninitialized_middle_range ... ok
test vm_storage::tests::read_sequential_range::read_uninitialized_end_range ... ok
test vm_storage::tests::read_sequential_range::read_uninitialized_range ... ok
test vm_storage::tests::read_sequential_range::read_uninitialized_start_range ... ok
test vm_storage::tests::remove_range::remove_multiple_slots_over_initialized_range ... ok
test vm_storage::tests::remove_range::remove_multiple_slots_over_partially_uninitialized_end_range ... ok
test vm_storage::tests::remove_range::remove_multiple_slots_over_partially_uninitialized_middle_range ... ok
test vm_storage::tests::remove_range::remove_multiple_slots_over_partially_uninitialized_start_range ... ok
test vm_storage::tests::remove_range::remove_multiple_slots_over_uninitialized_range ... ok
test vm_storage::tests::remove_range::remove_single_value_over_initialized_range ... ok
test vm_storage::tests::remove_range::remove_single_value_over_uninitialized_range ... ok

failures:

---- recovery::gas_price_updater__can_recover_on_startup_when_gas_price_db_is_ahead stdout ----
Stopping fuel service
Stopping fuel service
Stopping fuel service
Stopping fuel service
Stopping fuel service
Stopping fuel service
thread 'recovery::gas_price_updater__can_recover_on_startup_when_gas_price_db_is_ahead' panicked at tests/tests/recovery.rs:98:5:
assertion failed: database.on_chain().latest_height() < database.gas_price().latest_height()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Stopping fuel service
Stopping fuel service
Stopping fuel service
proptest: Saving this and future failures in /home/runner/actions-runner/_work/fuel-core/fuel-core/tests/proptest-regressions/recovery.txt
proptest: If this test was run on a CI system, you may wish to add the following line to your copy of the file.
cc 12ad604678b10444578675e798701e7d04a7c2ab772069f63045cc895686c406
thread 'recovery::gas_price_updater__can_recover_on_startup_when_gas_price_db_is_ahead' panicked at tests/tests/recovery.rs:131:1:
Test failed: assertion failed: database.on_chain().latest_height() < database.gas_price().latest_height().
minimal failing input: (height, lower_height) = (
    5,
    4,
)
	successes: 4
	local rejects: 0
	global rejects: 0



failures:
    recovery::gas_price_updater__can_recover_on_startup_when_gas_price_db_is_ahead

test result: FAILED. 234 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 500.01s

error: test failed, to rerun pass `-p fuel-core-tests --test integration_tests`