chore: ramp up the dark launch of the new socks proxy discovery to 10…

…0% (#4887)

**Background:**
See https://dfinity.atlassian.net/browse/NET-1765.

**State as of 23/4/2025:**
- The dark launch path gives a success rate of nearly 100% (while the
regular path stays at about 80%). Most of the regular path failures are
due to `NetworkUnreachable`.
- There was a [burst of mismatching http response
codes](https://kibana.mainnet.dfinity.network/app/r/s/DOmas) between the
regular path and the dark launch path. Almost all of them are 200 vs 400
HTTP codes, happening in the span of a few minutes on the 21st of April.
It was most likely a serverside hiccup. There were a total of 41
mismatches in the last week across all nodes, while there are on average
60 requests every minute, so this incident can be considered noise.

<img width="1321" alt="Screenshot 2025-04-23 at 15 08 43"
src="https://github.com/user-attachments/assets/6d236ddc-756c-40a6-a228-f9c47eb96906"
/>

<img width="1341" alt="Screenshot 2025-04-23 at 15 08 48"
src="https://github.com/user-attachments/assets/79c7f356-b8c2-4ea2-a7f7-c29bd4775156"
/>



TLDR: the dark launch works better than the regular path, nearly 100% of
all requests connect to the target server, and there are very few Http
code mismatches.

We ramp this up to 100%, meaning all requests will go via the API BNs
(still as a dark launch). This will stress the API BNs sufficiently to
prove they can handle full traffic.

fix: revert "chore: unifying downloading logic (#4805)" (#4836)

This reverts commit 943d3bf because it
breaks the `//rs/tests/nested:hostos_upgrade_smoke_test`.

Schedule Hourly: https://github.com/dfinity/ic/actions/runs/14490678316
✅ .

chore: Update Mainnet IC revisions file (#4806)

Update mainnet revisions file to include the latest version released on
the mainnet.

This PR is created automatically using
[`mainnet_revisions.py`](https://github.com/dfinity/ic/blob/master/ci/src/mainnet_revisions/mainnet_revisions.py)

Co-authored-by: CI Automation <[email protected]>

feat(PocketIC): new struct PocketIcState (#4708)

This PR introduces a new struct `PocketIcState` encapsulating the state
directory of a PocketIC instance. This encapsulation is particularly
useful when used with a temporary directory (the struct takes care of
creating a new temporary directory and deleting it automatically) and
also "documents" the flows (e.g., `PocketIcBuilder::with_state` takes
ownership while `PocketIcBuilder::with_read_only_state` only takes a
reference).

test(Ledger): FI-1689: Tests for archive chunking and ranges (#4678)

Adapt tests for archive chunking and archive ranges to support both the
ICP and ICRC ledger suites.

feat(nns): Define VotingPowerSnapshot and a collection of snapshots (#…

…4404)

# Why

To prevent a sudden takeover of the NNS in the event of some party
gaining illegitimate voting power (e.g. a bug in Governance, ICP Ledger,
etc.), we aim at reverting the voting power to an earlier snapshot, so
that neurons don't gain voting power immediately if a spike is detected.

# Related PRs

There are 3 PRs to achieve the above-mentioned goal:

- (current PR) Define VotingPowerSnapshot and a collection of snapshots
- (#4405) Add a timer task to record snapshots periodically
- (#4406) Use the previous snapshot if a voting power spike is detected

# What

* Define a VotingPowerSnapshot to represent the voting power calculated
at a certain point of time
* One key decision is to also snapshot the voting power of each neuron,
which then can be used to create ballots later, if (in an extremely
unlikely event) a voting power spike is detected
* Implement how the snapshot can be used:
  * Add a snapshot
* Check the last time the snapshot is added (for scheduling tasks to add
snapshots)
  * Check if the voting power has a spike

feat(icrc-rosetta): add icrc rosetta release 1.2.0 (#4652)

Release info for ICRC Rosetta 1.2.0

feat(icrc-rosetta): add icrc rosetta release 1.2.0 (#4652)

Release info for ICRC Rosetta 1.2.0

feat(PocketIC): new function PocketIcBuilder::with_read_only_state_dir (

#4495)

This PR adds a new function `PocketIcBuilder::with_read_only_state_dir`
to specify a directory from which the state of the PocketIC instance
should be loaded without modifying the provided directory (i.e., the
provided directory is "read-only"). This is useful, e.g., to resume
multiple instances from the same state concurrently (in which case
concurrent modifications of the same underlying state directory would
lead to data races).

feat(nns): Support initializing NNS Governance by candid (#4537)

# Why

NNS Governance almost use candid everywhere, except for 2 _pb methods
(being deprecated) and init. We would like to switch init to candid as
well.

# What

* Support candid parsing in init