fix: quote echo line in fips-smoke script to avoid YAML colon parsing

First pipeline failed with 'jobs:fips-smoke:script config should be a string or a nested array of strings up to 10 levels deep'. Root cause: an unquoted echo "fips-smoke: ..." script line, where the inner : made YAML parse the line as a mapping instead of a string.

Fix: wrap the script item in single quotes so YAML treats it as a literal string.

Verified locally: glab ci lint → "CI/CD YAML is valid!"