FTD-style: FlexConfig for what the manager has no screen for

Objectives

The simulator ticks each one as soon as the network meets it.

1. Try flexconfig EXTRAS add route outside 10.0.0.0 255.0.0.0 203.0.113.2. The manager refuses: routes have their own screen.
2. Add two lines to FlexConfig EXTRAS: same-security-traffic permit inter-interface, and no sysopt connection permit-vpn. Assign EXTRAS to FTD1.
3. Deploy. FTD1’s show running-config has both lines.
4. Add the line bogus command to FlexConfig BAD, assign it to FTD1, and deploy. The deployment fails with the reason, and FTD1 keeps what it had. Then remove BAD and deploy again.