unit test TestFormatWithInlineCryptoEngine failing

[frederic-hoerni]

The unit test TestFormatWithInlineCryptoEngine is failing when called this way:

$ go test ./internal/luks2 -check.v -check.f TestFormatWithInlineCryptoEngine
PASS: cryptsetup_test.go:602: cryptsetupSuite.TestFormatWithInlineCryptoEngine	0.025s

----------------------------------------------------------------------
FAIL: <autogenerated>:1: cryptsetupSuiteARM.TestFormatWithInlineCryptoEngine

using shellcheck: ""
cryptsetup_test.go:616:
    // feature detection
    c.Assert(mockCryptsetup.Calls(), HasLen, 3)
... obtained [][]string = [][]string{[]string{"cryptsetup", "--batch-mode", "luksFormat", "--type", "luks2", "--key-file", "-", "--cipher", "aes-cbc-essiv:sha256", "--key-size", "256", "--label", "test", "--pbkdf", "pbkdf2", "--pbkdf-force-iterations", "1000", "--luks2-keyslots-size", "2048k", "--inline-crypto-engine", "some-path"}}
... n int = 3

OOPS: 1 passed, 1 FAILED
--- FAIL: Test (0.04s)
FAIL
FAIL	github.com/snapcore/secboot/internal/luks2	0.050s
FAIL

Whereas it passes when called these ways:

$ go test ./internal/luks2 -check.v -check.f   cryptsetupSuite.TestFormatWithInlineCryptoEngine
ok  	github.com/snapcore/secboot/internal/luks2	0.034s
$ go test ./internal/luks2 -check.v -check.f   cryptsetupSuiteARM.TestFormatWithInlineCryptoEngine
ok  	github.com/snapcore/secboot/internal/luks2	0.034s

The impact is minor. It does not reveal any secboot bug, nor breaks the whole test suite.