Revert scheduled tests with 2/candidate

[roosterfish]

This PR reverts #1315.

By simply skipping the binary injection for 2/candidate, we don't anymore use the special test binary required for the test suite that runs in non-interactive mode. This will cause the tests to error as all microcloud * commands will launch in interactive mode.

As an example see https://github.com/canonical/microcloud/actions/runs/24138613221/job/70433996098.

[tugbataluy]

LGTM. I missed the non-interactive binary dependency when approving #1315, apologies.

[roosterfish]

LGTM. I missed the non-interactive binary dependency when approving #1315, apologies.

I should have spotted it beforehand.

Before we can enable this we need to make sure we can test with arbitrary snap versions without injecting a custom test binary that accommodates the test suite.
We could enable the testing mode inside the shipped snaps so when you use TEST_CONSOLE=1 it switches into this mode.

IIRC back then this wasn't added to the snap's binary to ensure the trust establishment cannot be shortcut as setting TEST_CONSOLE=1 will also assume a passphrase of a a a a which makes testing easier as we don't always have to grab the random passphrase from stdout.

[simondeziel]

Would it be possible to MICROCLOUD_DEBUG_PATH=/snap/microcloud/current/...?

This would sideload the same binary as shipped by the snap.

[roosterfish]

Great idea, but the binary in the snap doesn't contain the bits that allow it being put into testing mode (not built with -tags=test).

[simondeziel]

We could enable the testing mode inside the shipped snaps so when you use TEST_CONSOLE=1 it switches into this mode.

IIRC back then this wasn't added to the snap's binary to ensure the trust establishment cannot be shortcut as setting TEST_CONSOLE=1 will also assume a passphrase of a a a a which makes testing easier as we don't always have to grab the random passphrase from stdout.

If grabbing the random passphrase from stdout is feasible, that sounds like the best way forward to me.

[roosterfish]

If grabbing the random passphrase from stdout is feasible, that sounds like the best way forward to me.

Actually this is how we did it from the start when adding trust establishment. But later we removed those bits from the binary which is shipped with the snap.
I have added #1320 so we can address this properly.