The TC wants to ensure that the amount of assignments by validators to parachains is at a maximum in order to reduce the possibility of a network issue: This proposal ensures that before the next runtime upgrade. 

Right now the way we have validators assigning on Kusama is overzealous: everyone is assigning to check the 1 parachain Kusama has. With 2 chains, we expect 1/2 of them will assign, and so on. 

We're already at the maximum of assignments, so the TC wants to correctly track the 40 parachain groups we have on the Network (200 validators / 5 per group) by the next runtime upgrade to ensure finalization.

Once we deploy the new changes + a node update, we can start to bring this value down (to something like 5 or 10).

This proposal:

* It's changing a parachain configuration in advance to match an upcoming runtime change.
* It will have no effect on current behavior.

Preimage can be found [HERE](https://drive.google.com/file/d/1381AEjaUKxXkmgKYr5J_WFLrcGNRFfS0/view?usp=sharing).

- The TC wants to make sure there are not too many assignments for validators on the network.
- Right now, all validators are assigning to one parachain, but with more parachains, they will assign to fewer.
- The TC wants to track the 40 parachain groups on the network by the next runtime upgrade.
- After the upgrade, they will reduce the number of assignments to 5 or 10.
- This proposal will not change anything right now, but it prepares for future changes.

#300 Configuration change requested by Technical Committee