Extend static Router Container impairment coverage in Scenario File

[rishabh-slamcore]

What to build

Extend the same nested network_impairment mapping so an invocation can express the remaining static Router Container impairment options after the initial subset lands.

This slice expands support to:

• jitter and delay distribution
• loss correlation
• reordering
• duplication
• corruption

The Docker runtime should map these options onto static tc netem configuration at the Router Container.

Reference examples

These examples define the intended impairment semantics for this slice:

# Latency with jitter
tc qdisc add dev eth1 root netem delay 100ms 20ms

# Latency with jitter — gaussian
tc qdisc add dev eth1 root netem delay 100ms 20ms distribution normal

# Packet loss — correlated consecutive loss
tc qdisc add dev eth1 root netem loss 5% 25%

# Packet reordering
tc qdisc add dev eth1 root netem delay 10ms reorder 25% 50%

# Packet duplication
tc qdisc add dev eth1 root netem duplicate 1%

# Packet corruption
tc qdisc add dev eth1 root netem corrupt 0.1%

Acceptance criteria

• The network_impairment mapping can express jitter and delay distribution.
• The network_impairment mapping can express correlated loss.
• The network_impairment mapping can express reordering, duplication, and corruption.
• The Docker invocation runtime applies the expanded static impairment options at the Router Container.
• Invalid advanced impairment combinations fail loudly during Scenario File validation.
• Tests cover the expanded impairment options and preserve compatibility with the first-slice subset.

Blocked by

• Expand Scenario File with static Router Container impairment subset #24