feat(spike): cross-chain nonfungible implementation

[chungquantin]

Description

Blocked by: #387

Context: Why can't we use the default NonFungiblesTransactor provided by the xcm crate? Current asset transactor for nonfungible implementation is currently only for nonfungibles, not nonfungibles_v2. If we want it to support latest the version of the pallet-nfts crate (collection management functionalities), we need to reconstruct the NonFungiblesTransaction.

The pull request implements the NonFungiblesTransactor using the ForeignNfts pallet nfts instance. This makes changes to the pallet-nfts CollectionId type to remove the Copy required parameter trait as xcm::latest::Location is not implemented with Copy. Replace all the copies of CollectionId in the pallet-nfts code to use Clone. Performance benchmarking should be considered to see if there is a huge change in the memory efficiency.

• MultiLocationCollectionId implemented with xcm::latest::Location
• NonFungiblesTransactor
• ForeignNfts instance and runtime configuration
• XCM simulator integration tests

Outcome

[chungquantin]

Because if the incrementable can be removed it would not be necessary to implement the MultiLocation(Location) type

You can view the changes if we remove the incrementable trait here #406. Imo, the current approach in this PR is cleaner as it does not remove any thing related to functionality in the pallet-nfts, mainly changes in the CollectionId trait and data ownership.