Add "message priority" three levels of message priority

[MaxpowerxaM]

Currently, sending a message incurs a fixed minimum cost that might lead to inefficiencies in message delivery times as the adoption of the Kaspa network grows over time. To address this issue, at least three levels of structured priority should be implemented as follows:

• Priority Level 1: Costs must be reduced to the absolute minimum necessary for users to communicate without concerns about potential network congestion. Ideally, this would involve a fixed fee.

• Priority Level 2: Costs must enable users to send messages comfortably without experiencing significant delays. The message cost should be calculated based on a 30-day average and updated daily by scanning the network to determine the new cost using data from the previous 30 days.

• Priority Level 3: Costs must allow users to send messages with maximum priority. These costs should be recalculated every hour, taking into account actual network congestion. The calculation formula could be: AVERAGE COST OVER THE LAST 24 HOURS * 2.

• Priority Level 4: The cost is a fixed amount determined by the user.

Additionally, it will be necessary to establish a parameter called max_priority_cost, set by default at 1KAS, ensuring that automatically calculated costs remain within acceptable limits.