fix(s003): the image's self-check matches enable_fips_mode/1's true

The final RUN matched ok where crypto:enable_fips_mode/1 returns true,
so the first fips-image run (35536968071) failed at the check after a
complete build. Measured locally: the image now builds through the
check.

Signed-off-by: Ayla Croft <aylacroft@proton.me>

Author: HackTuah

ci/fips/Containerfile

@@ -66,5 +66,5 @@ RUN mix local.hex --force && mix local.rebar --force
 # entering FIPS mode is possible. Which mode a container runs in is the leg's decision, made
 # by OPENSSL_FORCE_FIPS_MODE and `-crypto fips_mode true` at run time, never here.
 RUN erl -noshell -eval \
-      'true = maps:get(fips_provider_available, crypto:info()), ok = crypto:enable_fips_mode(true), enabled = crypto:info_fips(), io:format("~p~n", [crypto:info()]), halt().' \
+      'true = maps:get(fips_provider_available, crypto:info()), true = crypto:enable_fips_mode(true), enabled = crypto:info_fips(), io:format("~p~n", [crypto:info()]), halt().' \
     && elixir --version