Add extension set support to activation tests

[singerb]

Requires https://github.com/Automattic/compatibility-dashboard/pull/1196

Fixes https://github.com/Automattic/woocommerce.com/issues/22982

This PR allows the local activation test running to use the --extension_set argument. It relies on this information being added to the sync data in the linked PR. Note that this relies on the usual access controls in order to be able to download the extensions listed in the set, so most vendor accounts will not be able to use it.

Testing:

• Deploy the linked PR to staging.
• Switch your backend to staging and/or resync.
• Test ./qit run:activation --extension_set=minimal <extension to test>; verify that the extra extensions get activated during the test steps.
• Verify a run without an extension set still works as expected.
• Test around this issue.

[singerb]

@Luc45 I may need some notes here on how to get phpunit to pass; looks like an ordering issue with the commands?

[zhongruige]

Tested great for me, happy to add my approval so it's ready to go once the unit tests are figured out.

[MrJnrman]

looks like an ordering issue with the commands?

Looks like you're missing the option declaration extension_set option from the UpEnvironmentCommand class.

[MrJnrman]

Tested and works great! Unit tests seem to be a quick fix so I'm happy to add a approval. Feel free to merge once you get the tests to pass

[singerb]

looks like an ordering issue with the commands?

Looks like you're missing the option declaration extension_set option from the UpEnvironmentCommand class.

No that should be there; it's dynamic from the schema.

[Luc45]

@singerb I'm looking into those tests now.