Improved integration test coverage for farm build functionality.

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 build are performed; that
    they are of the correct architecture; and that the builds occur
    on the expected node, given the build parameters that were supplied.

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.

Signed-off-by: Kevin Crocombe <kevin.crocombe@pegortech.co.uk>

Author: kcrocombe

docs/source/markdown/podman-farm-build.1.md.in

@@ -143,7 +143,7 @@ This option specifies the name of the farm to be used in the build process.
 
 #### **--local**, **-l**
 
-Build image on local machine as well as on farm nodes.
+Build image on local machine as well as on farm nodes (Default: true).
 
 @@option logfile