Add token transferable flag to NFT and SFT pallets

[JasonTulp]

Description

• This PR adds token level control over the ability to transfer NFT or SFT tokens. This is achieved by adding a set_token_transferable_flag extrinsic to each pallet.

Context & Background

• Previously we had this functionality at the collection level, however in a move towards supporting Soulbound EIP-5484 tokens, this will need to be added at the token level.

Notes & Additional Information

• To prevent storage migrations when adding soulbound tokens, and to optimise storage read/writes, the TokenUtilityFlags struct includes TokenBurnAuthority field which is currently unused.
• Variable benchmarks have been added to the NFT.transfer benchmark to account for the extra storage read per serial_number
• Currently the set_token_transferable_flag extrinsic is only callable by the collection owner. In future, this ownership model may be expanded to allow for more granular permissions control.

Related Issues

• https://futureverse.atlassian.net/browse/TRN-877?atlOrigin=eyJpIjoiMGEwZDBmZmFhOGY5NGQ1NWFkYjFkM2ZhNGY2ZmViYWUiLCJwIjoiaiJ9

---

Release Notes

Key Changes

Type of Change

• Runtime Changes
• Client Changes

API Changes

Storage Changes

Added

• Nft: TokenUtilityFlags
• Sft: TokenUtilityFlags

Extrinsic Changes

Added

• Nft: set_token_transferable_flag
• Sft: set_token_transferable_flag

Event Changes

Added

• Nft: TokenTransferableFlagSet
• Sft: TokenTransferableFlagSet

---

[surangap]

lgtm. need ci bench

[JasonTulp]

Changes from this PR are included in the soulbound changes: #928