Fix budget issue with Nested NFTs

[HashWarlock]

Description

There are 2 problems with the current Budget trait:

1. NFTs are currently allowed to mint and send NFTs to a parent NFT that can meet up to the threshold of NestingBudget::get() + 1. This allows for NFTs queries like lookup_root_owner to return errors like TooManyRecursions. Having this error is okay, but the NFTs should be prevented from being minted to or sent to a parent NFT if the Budget threshold is met.

2. Currently the code will do a calculation on functions like burn_nft and this will perform an arithmetic subtraction at the end of the function, but this should be added as a field in the Value type & implement a function from Budget to get the budget that has been consumed and budget that is left.

Target

• Fix minting/sending NFTs that exceed the threshold of NestingBudget::get() value.
• Add fields names budget_consumed and budget_left` to track & through errors is an overflow is detected.
• Add functions in Budget trait to get the 2 new fields.

[HashWarlock]

@Index0011 how does this look? Think it is okay to merge now?

[Index0011]

LGTM，I think