Add hack script to build hive install-log-regexes from ARO definition

[tsatam]

This is a spike PR to evaluate feasibility/desirability of a "single source of truth" for our install failure definitions, which can then be used by both our Hive setup as well as the RP. It should not be merged as-is for now.

Which issue this PR addresses:

Building block for ARO-3220

What this PR does / why we need it:

• Adds a definition for ARO-specific install failure reasons, maintained in Go, that defines specific regular expressions to identify reasons from a failed install's log.
• Adds a hack script to build a Hive additional-install-log-regexes ConfigMap, to supersede the default rules provided by Hive with ARO/Azure-specific cases, populated from the above definitions.

This work item will eventually involve building RP-side handling for these install failures, to directly alert customers when the reason is customer-inflicted, that will also build off of these definitions. The work will either be a part of a future PR or future commits on this branch, TBD.

Test plan for issue:

• Unit tests have been added for the regular expressions themselves (against "fake" install logs), as well as for the generator's conversion logic.
• The generated additional-install-log-regexes ConfigMap has been tested in a Hive cluster and ARO cluster creations have been performed that reproduce the scenarios within this PR, and validate that Hive has propagated the expected Reasons.

Is there any documentation that needs to be updated for this PR?

No.

[tsatam]

Changes included in #3116