feat: Bucket level read access

[snowmead]

This PR adds pallet_nfts (FRAME pallet) and pallet_bucket_nfts (wrapper around the NFTs pallet) to the runtime, fulfilling the need to distribute NFTs/items to users whom a bucket owner wishes to grant read access to.

Bucket NFTs Pallet

The reason for creating a new bucket NFTs pallet, is to provide ergonomic extrinsics which dApps and parachains can call and be certain they have not missed any underlying requirements which StorageHub imposes related to managing NFTs. While the pallet is small, and is mostly a wrapper around the NFTs pallet, it could potentially grow overtime catering to new unforseen usecases.

As of right now, this first iteration ensures the proper metadata is set to the items created within collections corresponding to a bucket. The only metadata required for MSPs to properly respond to user requests, is the read_access_regex. A finite byte field which determines which files a user owning this item has access to. Without this particular field, users would be denied all read requests sent to MSPs.

NFTs Pallet (FRAME)

While we do offer ergonomic extrinsics within bucket NFTs pallet, users and bucket owners can always directly call into the NFTs pallet. While it was first decided to disable the NFTs pallet extrinsics which would force our pallet to implement a lot of redundant logic, it is not insecure nor breaking to have users bypass the bucket NFTs pallet. They would only have to ensure they meet the requirements set by StorageHub (e.g. read_access_regex).

This enables all the features already offered by the pallet and greatly increases the potential use cases of StorageHub.

Notable Features

File System Pallet Extrinsics:

• create_bucket: Allows users to create private or public buckets, which determines whether to create a corresponding collection in the NFTs pallet.
• update_bucket_privacy: Enables users to update the privacy settings of their bucket post-creation.
• create_and_associate_collection_with_bucket: Allow users to create a new collection and associate it with a bucket. This is helpful when you want to overwrite a collection or a set one when there is none present set to the bucket (this can happen when the bucket is private and a user deletes the collection by calling the NFTs pallet directly).

Bucket NFTs Pallet Extrinsics:

• share_access: Allows bucket owners to share access by setting a read_access_regex on a newly created item in the NFTs pallet, owned by the recipient account.
• update_read_access: Lets bucket owners update the read_access_regex of any item in the collection. Options include None (no access) and Some(regex).

Bucket ID Generation:

• Bucket IDs are derived using the derive_bucket_id trait method from ReadProvidersInterface, implemented by the Providers pallet. This method hashes (Hasher - $H$) the concatenation of the owner (AccountId - $A$) and bucket name (Bucket name - $B$):
  $$\text{BucketId} = H(A, B)$$

Other unrelated features

File system pallet now uses provider Ids across the board instead of the base provider account Ids.

[ffarall]

Merge from main, solve conflicts and ready to go. Great work!