Database API call nft_get_all_tokens() should have limits

The Database API function nft_get_all_tokens() will currently return an array of NFT objects encompassing the entire set of existing 1.31.x NFT objects. In the event that the chain has more than a few hundred, few thousand, few million NFTs... this large of a return object may be disruptive and may become a way to DOS a node.

nft_get_all_tokens() — declaration, definition

Suggestion: implement limits

It might be a good idea to add limit and lower bound parameters to the nft_get_all_tokens() call, similar to what exists for list_offers() (declaration, definition). Then the client could request a desired quantity of NFT objects, starting from some initial object id.