Introduce delegating resource usage right

Simple Summary

The resource usage right can be delegated.

Motivation

After Stake 2.0 is enabled, the resource delegations have been much more flexible on the TRON network. The volume of resource delegation and revoking resource delegation transactions has increased significantly. Especially in the case of asset aggregation of an account, it needs to repeatedly delegate resources to other addresses and then undelegate after the transfer transactions are done, which makes large amounts of transactions happen and the operations could be very cumbersome. In order to alleviate this situation, it is proposed to introduce a new transaction type to reduce the number of such large and frequent resource delegation and revoking resource delegation transactions.

After introducing the transaction type of delegating resource usage right, when an account has to regularly initiate large amounts of resource delegation transactions to help other addresses execute transactions, it only needs to delegate the resource usage right to every target address once and for all. It will greatly reduce the complexity of the operations.

Specifications

Adding a transaction type of resources usage right delegation, it allows account A to delegate X shares of specific resources to account B. After the transaction is completed, the X shares of resources are still in account A, and when account B needs to consume the specific type of resources, resources less than X share will be consumed directly from account A first. When the resources to be consumed are greater than X share or account A has insufficient resources, account B's own resources will then be consumed.

The issue names no files, tests, or implementation entry points. Start by reading the resource delegation specification and locating the existing resource delegation transaction handling; done means the proposed delegating resource usage right transaction is supported with the described fallback consumption behavior.