[sozo] expose fee multiplier for sozo migrate

[glihm]

Is your feature request related to a problem? Please describe.
sozo migrate command does have a fee multiplier in the code, but it's not exposed to the user.
This can cause trouble when migrating to a Katana with fees activated or a Starknet network.

Describe the solution you'd like
In a first step, this PR should expose the fee multiplier to the user.
In a second PR, we may want to use the raw fee or fee multiplier, introduced in #1601.

Additional context
The apply_diff function has a TxConfig which contains a fee multiplier field.
It is set to None. The modification should make this field coming from the CLI.

dojo/crates/sozo/ops/src/migration/mod.rs

Lines 275 to 280 in f0637f9

	pub async fn apply_diff<P, S>(
	ws: &Workspace<'_>,
	account: &SingleOwnerAccount<P, S>,
	txn_config: Option<TxConfig>,
	strategy: &mut MigrationStrategy,
	) -> Result<MigrationOutput>

[kariy]

Fee multiplier already exist in the TransactionOptions:

dojo/bin/sozo/src/commands/options/transaction.rs

Lines 6 to 13 in 64fa43c

	pub struct TransactionOptions {
	#[arg(long)]
	#[arg(value_name = "MULTIPLIER")]
	#[arg(help = "The multiplier to use for the fee estimate.")]
	#[arg(long_help = "The multiplier to use for the fee estimate. This value will be used on \
	the estimated fee which will be used as the max fee for the transaction. \
	(max_fee = estimated_fee * multiplier)")]
	pub fee_estimate_multiplier: Option<f64>,

iirc sozo migrate used to accept the tx config along with the multiplier.

[glihm]

Fee multiplier already exist in the TransactionOptions:

dojo/bin/sozo/src/commands/options/transaction.rs

Lines 6 to 13 in 64fa43c

	pub struct TransactionOptions {
	#[arg(long)]
	#[arg(value_name = "MULTIPLIER")]
	#[arg(help = "The multiplier to use for the fee estimate.")]
	#[arg(long_help = "The multiplier to use for the fee estimate. This value will be used on \
	the estimated fee which will be used as the max fee for the transaction. \
	(max_fee = estimated_fee * multiplier)")]
	pub fee_estimate_multiplier: Option<f64>,

iirc sozo migrate used to accept the tx config along with the multiplier.

Yeah good point, I think it was a regression here. I've added it back into #1802.

From the conversation we had in the discord with the community, I think we should add in the TransactionsOptions a raw max fee to ensure it can be set independently of the node capabilities to estimate fee. Sounds good to you @kariy?

Will open an issue for this next task if you agree.

[kariy]

From the conversation we had in the discord with the community, I think we should add in the TransactionsOptions a raw max fee to ensure it can be set independently of the node capabilities to estimate fee. Sounds good to you @kariy?

Will open an issue for this next task if you agree.

Yeah, we thought about adding this before when we're adding the multiplier flag. Sounds good to me

[glihm]

Will close in this one is favor of #1808.