Improved integration test coverage for farm build.

[kcrocombe]

Existing integration test cases for farm functionality is limited to the operations that create/update/delete farm objects. There is no test coverage of any actual farm builds.

This submission seeks to address this via the addition of a new integration test module: farm_build_test.go

This module:

• prepares a simulated, multi-farm, multi-node test environment
• performs testing of the podman farm build function across that environment.
• confirms that the expected number of builds are performed; that they are of the correct architecture; and that they built on the expected nodes, as determined by the supplied parameters.

The commit also includes two minor changes:

• A very minor change the farm documention to clarify one of of the default setting.

• The farm system-test script 001-farm.bats now uses an explicitly set connection name rather than relying on the default in the users environment being set in a supportive manner.

THIS SUBMISSION MAKES NO CHANGES TO THE PRODUCT CODE BASE.

Does this PR introduce a user-facing change?

None

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[baude]

i think the three stanzas can be grouped as one

[kcrocombe]

Thanks. I've never written Go before, so any style tips, pointers etc. gratefully received.

[baude]

same here

[kcrocombe]

/hold
Investigating the additional commits - suspecting rebase snafu

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kcrocombe

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment