Fix error log parsing in compute build CI

[DavidHuber-NOAA]

Description

This PR adds a new feature to capture and report which compute builds failed when running CI.

Resolves #3296

Type of change

• New feature (adds functionality)

Change characteristics

• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO
• Does this change require an update to any of the following submodules? NO

How has this been tested?

• CI on Hercules

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have documented my code, including function, input, and output descriptions
• My changes generate no new warnings
• New and existing tests pass with my changes
• This change is covered by an existing CI test or a new one has been added

[DavidHuber-NOAA]

Running CI on Hercules to test the new feature.

[emcbot]

Build FAILED on Hercules in Build# 1 with error logs:

/work2/noaa/global/CI/HERCULES/3301/global-workflow/sorc/logs/gdas.log

Follow link here to view the contents of the above file(s): (link)

[DavidHuber-NOAA]

Testing on Hercules shows that these changes successfully triggers the creation of a gist with the failed log file. Marking this PR as ready for review.

[TerrenceMcGuinness-NOAA]

Yes I saw the error logs showed up and got stored in the Jenkins Artifacts, saved of the main log file to the records repo, and created the gist to boot. And now works in concert with the updates that also catch the case where there are no logs. Looks great!