This plugin is not auto-activated on new networks when created via WP-CLI

[christianwach]

Here's another UI/CLI parity conundrum...

When creating a new network via the UI, this plugin auto-activates itself on the new network. When doing so via WP-CLI, it does not. I realise it's possible to do this with another WP-CLI command after creating the new network, but it means parsing the new network ID out of the CLI return, then issuing the command.

I wonder if it would be sensible also to auto-activate by default in WP-CLI? I support this idea (for parity with the UI and therefore with people's expectations) but you may think otherwise.