chore: dag block proposal limit

[mfrankovi]

On high transactions per second load on the network dag block and transactions packets start queueing up in the packet queue. This causes delays in receiving DAG block packets which makes nodes propose dag blocks with high difficulty or even stale since the low difficulty dag blocks are not received in time. This causes a chain reaction with more dag block being produced it is less likely for the network to digest it in time. At the same time this causes a large build up of non-finalized dag blocks ans transations.
To prevent this:
Node is not to produce a dag block if the queue is over the queue limit
Node is not to produce a dag block if total non finalized transactions are over the limit

[taraxadeploy]

prnet cleaned-up successfully