THIS PROPOSAL IS BROKEN. PLEASE DO NOT ENDORSE.

A new year rolls around and Zeitgeist reorganizes the Advisory Committee to optimize the deployment process of curated markets and the flow of liquidity. The remaining market is controlled by key personnel who will be overseeing the curation of markets.

Set the collective's membership.

- `new_members`: The new member list. Be nice to the chain and provide it sorted.
- `prime`: The prime member whose vote sets the default.
- `old_count`: The upper bound for the previous number of members in storage. Used for
  weight estimation.

Requires root origin.

NOTE: Does not enforce the expected `MaxMembers` limit on the amount of members, but
      the weight estimations rely on it to estimate dispatchable weight.

# WARNING:

The `pallet-collective` can also be managed by logic outside of the pallet through the
implementation of the trait [`ChangeMembers`].
Any call to `set_members` must be careful that the member set doesn't get out of sync
with other logic managing the member set.

# <weight>
## Weight
- `O(MP + N)` where:
  - `M` old-members-count (code- and governance-bounded)
  - `N` new-members-count (code- and governance-bounded)
  - `P` proposals-count (code-bounded)
- DB:
  - 1 storage mutation (codec `O(M)` read, `O(N)` write) for reading and writing the
    members
  - 1 storage read (codec `O(P)`) for reading the proposals
  - `P` storage mutations (codec `O(M)`) for updating the votes for each proposal
  - 1 storage write (codec `O(1)`) for deleting the old `prime` and setting the new one
# </weight>

- Problem Statement: Inefficient deployment process and liquidity flow within the Advisory Committee.
- Significance: Lack of optimization in market curation and liquidity management.
- Proposed Solution: Reorganize the Advisory Committee for better deployment and liquidity flow.
- Expected Outcomes: Improved market curation and enhanced liquidity management.

#54 [BROKEN] Reorganize Advisory Committee

No Active Proposals