Implement own RemovePallet logic taking into account limit value

[dmitrylavrenov]

Thanks @quasiyoke by noting that consumed weight is much higher than a total weight at #1433 (comment). The root cause comes from #1434.

Proposing to add RemovePallet based on [frame_support::migrations::RemovePallet], but doesn't focus just on removing all storage items per one runtime upgrade in one block. Additionally, it allows to use capabilities of clear_prefix with limit that can be used to partially delete a prefix storage in case it is too large to delete in one block.

try-runtime over current master with offences removal

2025-02-18 13:04:47.930  INFO main try-runtime::cli: TryRuntime_on_runtime_upgrade executed without errors. Consumed weight = (**10102150000000** ps, 0 byte), total weight = (**2000000000000** ps, 18446744073709551615 byte) (**505.11 %**, 0.00 %).    
Test succeeded

try-runtime over proposed code with offences removal

2025-02-18 16:01:30.514  INFO main try-runtime::cli: TryRuntime_on_runtime_upgrade executed without errors. Consumed weight = (**1250375000000** ps, 0 byte), total weight = (**2000000000000** ps, 18446744073709551615 byte) (**62.52 %**, 0.00 %).    
Test succeeded

[dmitrylavrenov]

It's better to wait substrate deps update containing - https://github.com/paritytech/substrate/issues/13690 instead of doing it by ourself for now

[MOZGIII]

Please create an issue for this

[dmitrylavrenov]

https://github.com/paritytech/substrate/issues/13690

Sure - #1447