Updating the list of public subnets

[sat]

This proposal is in line with:

Suggested approach to make more compute capacity available on the IC

TL;DR Given the rapidly increasing load on the IC, we propose adding additional application subnets to provide developers with greater flexibility and choice when selecting a deployment environment. This expansion will increase the capacity of ICP and accommodate continued growth in the coming months. The following three step approach is proposed: Step 1: Expand the list of public subnets. This step has already been completed Step 2: Open subsets of the currently verified subnets to the commun…

Additional comment: @nikola-milosa in

feat(dre): incremental opening of verified subnets

added two features:

1. querying the CMC canister for the list of current public subnets, which allows the tooling to show the transition of the Public setting (e.g. false ⇒ true) based on the real setting at the time of the proposal submission
2. allows us to make 1 “verified” subnet at a time (naming is hard, let’s not talk about the choice of word “verified”)

The shefu subnet is not yet public, in line with the explanation in

feat: Restrict legacy ICQC code to one subnet (#2647)