hack: use double space in ytt checksum check

[cirocosta]

even though standard gnu coreutils accepts taking a single space as the
separator, that's not true for busybox.

by making sure we're passing a double space everywhere we compute a
checksum, we """guarantee""" to be good not only w/ gnu, but also
busybox-based ones (like alpine etc).

				filename_ptr = strstr(line, "  ");          // double space
				/* handle format for binary checksums */
				if (filename_ptr == NULL) {
					filename_ptr = strstr(line, " *");

(see https://github.com/mirror/busybox/blob/15f7d618ea7f8c3a0277c98309268b709e20d77c/coreutils/md5_sha1_sum.c#L296)

ps.: in case you're wondering why this isn't captured by CI, it's because
we have github running based of ubuntu:

jobs:
  build:
    runs-on: ubuntu-latest

[netlify]

✔️ Deploy Preview for elated-stonebraker-105904 canceled.

🔨 Explore the source changes: 9de1744

🔍 Inspect the deploy log: https://app.netlify.com/sites/elated-stonebraker-105904/deploys/618d3912fcae130007617c99

[emmjohnson]

How to ensure we wont have a regression here?

[waciumawanjohi]

How to ensure we wont have a regression here?

We could add a self-hosted busybox runner and have our workflows randomly assign the job to the default runner or the self-hosted runner...

Note: Github discourages self-hosted runners for public repos.

[cirocosta]

yeah that's a good point - internally we make use of it in GitLab, so there's some form of coverage there that would surface here for sure