Ensure buildlogger uses available masks (issue reported by Christian Sousa from Blue Origin Manufacturing, LLC)

What does this MR do?

There's a few scenarios where we need a buildlogger, but it's "incomplete" in the sense that we might not have resolved all secrets.

This ensures that in these situations, we create a new buildlogger with the information we have available.

Why was this MR needed?

Some secrets were not being masked in rare circumstances.

What's the best way to test this MR?

• go test -run TestBuildMasking/failed --tags integration -v ./executors/docker against main branch will failure.
• In this MR, the above test will run and mask the terminating job error message for a failed job, to prove that it is capable of now doing so.

What are the relevant issue numbers?

Closes #39081