INV4 v2

[arrudagates]

This issue will keep track of progress towards the INV4 v2 implementation, along with discussions of the feature set and design decisions.

• [ ] Replace voting logic with pallet-ranked_collective, while having the ranked-collective ranks and rank weight inputs come from INV4 itself, thus keeping the original logic of INV4 and only delegating the raw voting logic to ranked-collective as a better standardized API.
• [ ] Refactor the voting weights to implement CurrencyToVote instead of raw Balance
• [ ] Detach IPF and RMRK from INV4 and instead replace with a cusotm trait that requires the implementastion of all the necessary functions for NFTs on pallet-inv4, making INV4 a true generalized NFT wrapper where NFT pallets implement the INV4 trait in the runtime and plug into an enum also defined in the runtime
• [ ] Implement a track system similar to pallet-referenda's so that we can customize parameters like amount of multisig calls allowed concurrently for each different subtoken
• [ ] Research and implement an efficient system for fully customizable user provided call filters for each track, similar to the current permissions system, but with an extensive rule system. See https://github.com/InvArch/InvArch-Frames/discussions/186
• [ ] Simplify IPS multisig fee system by removing the whole logic of distributing the call fee among voters and instead just take the fee from the multisig account by proceeding with the call naturally
• [ ] Rethink origin types for a more flexible account representation, using XCM's Plurality junction seems to be a great way to represent calls made by the multisig, as we can have an implementation that always derives the same account while the plurality can still dynamically represent different things, like different groups within the same IP Set and even different voting ratios. This would eliminate a bunch of checks and also make multisigs extremely powerful, while also preparing them for XCM transactions.