Change tip alert

[PhilippeR26]

Motivation and Resolution

Devs are complaining to have a flood of error messages when using snjs Devnet, integration or Testnet networks.
Estimation of tip is optimized for Mainnet, but is generating a lot of error messages when using other networks, due to a low quantity of transactions per block.
To be less disruptive for devs, I propose to replace the error message by a warning message.

Usage related changes

In node.js, jest tests, browser console, very aggressive error messages are now replaced by warnings.

Development related changes

Note

starknet.js/src/provider/modules/tip.ts

Lines 386 to 392 in 27f2a9b

	if (allTips.length < minTxsNecessary) {
	logger.error(
	`Insufficient transaction data: found ${allTips.length} V3 transactions with tips in ${blocksAnalyzed} blocks ` +
	`(block range: ${Math.max(0, startingBlockNumber - maxBlocks + 1)}-${startingBlockNumber}). ` +
	`Required: ${minTxsNecessary} transactions. Consider reducing minTxsNecessary or increasing maxBlocks.`
	);
	return createZeroTipEstimate(blocksAnalyzed, allTips);

I ask me if it's a good idea to return a zero value if not enough txs have been found.
It could be better to respond zero only if nothing has been found, and in other cases, try to calculate the tip.

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• All tests are passing

[tabaktoni]

Sure, it's fine.
It was important when we migrated to the fee mechanism for devs to be aware, but now it is time to switch to warn.

[github-actions]

🎉 This PR is included in version 9.0.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀