CI: Optimize use of autoconf caching

[jimklimov]

Follow-up to PR #3109 for issue #3108, which added ways to cache autoconf discovery/configuration results (among other achievements).

While that PR did address the subject area in broad strokes, cached rebuilds on some systems did complain about effective loss of some configuration nuances, because thise values were set when running cacheable logic - and so never tickled in cached runs. This is effectively due to an old mis-use of those autotools methods (which are documented to require that nothing consequential happens in their optionally-called code).

This PR aims to make rebuilds with same config reproducible (in terms of populating same definitions in config.log, config.h, etc.) by more diligently coding the population vs. use of cached data. As a significant starting point seen as a bottleneck in eyeball profiling, probably related to numerous calls to pre-processor, compiler or linker, various m4/nut_check_lib*.m4 files were revised for this PR.

Further improvements may be possible around:

• boolean support (probably to be done as part of Refactor code from custom bool_t to stdbool.h (where available) #1176 / Consolidate bool_t definitions into a common header file #31 which may remove much of this code),
• documentation generation ability testing (e.g. a2x calls for man pages),
• systemd unit file syntax support checks,
• compiler tests seem to pause in the beginning (pragmas are cached and go fast on re-runs),
• cppunit support,
• investigate the long pause between "egrep support" and "CONFIG_FLAGS" report (first 3 or so lines of output) - likely this is where configure loads and parses the cache, but maybe there is something we do that can save some time (e.g. several calls to gitlog2version.sh may happen there and maybe can be revised into one run and then populating the data points from cache?
• simple profiling is doable with bash 5+ loops: ./configure ... 2>&1 | while read LINE ; do echo "[$EPOCHREALTIME] $LINE" ; done -- but should not be done with date calls (expensive, skews the result). Maybe adapting the https://github.com/marcomorain/tcat/blob/master/tcat.c project to print higher-precision timestamps (like NUT upsdebugx does) is a decent option too.

Also some typos and bugs were noted and addressed.

[github-actions]

A ZIP file with standard source tarball and another tarball with pre-built docs for commit 3841ce2 is temporarily available: NUT-tarballs-PR-3428.zip.

[AppVeyorBot]

✅ Build nut 2.8.5.4661-master completed (commit 2d1da9e83b by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4661-master.7z

[AppVeyorBot]

✅ Build nut 2.8.5.4662-master completed (commit 1971357864 by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4662-master.7z

[AppVeyorBot]

✅ Build nut 2.8.5.4663-master completed (commit 55dfd0b1bd by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4663-master.7z

[AppVeyorBot]

❌ Build nut 2.8.5.4666-master failed (commit fb5ef643d1 by @jimklimov)

• artifacts (if any)

[AppVeyorBot]

❌ Build nut 2.8.5.4666-master failed (commit fb5ef643d1 by @jimklimov)

[AppVeyorBot]

❌ Build nut 2.8.5.4667-master failed (commit 309b0787c5 by @jimklimov)

• artifacts (if any)

[AppVeyorBot]

✅ Build nut 2.8.5.4668-master completed (commit d13bfc1c9c by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4668-master.7z

[AppVeyorBot]

✅ Build nut 2.8.5.4668-master completed (commit d13bfc1c9c by @jimklimov)

[AppVeyorBot]

✅ Build nut 2.8.5.4669-master completed (commit ed2a7d8043 by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4669-master.7z

[AppVeyorBot]

❌ Build nut 2.8.5.4670-master failed (commit 79bbf82aae by @jimklimov)

• artifacts (if any)

[AppVeyorBot]

❌ Build nut 2.8.5.4670-master failed (commit 79bbf82aae by @jimklimov)

[AppVeyorBot]

✅ Build nut 2.8.5.4671-master completed (commit 79bbf82aae by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4671-master.7z

[AppVeyorBot]

✅ Build nut 2.8.5.4671-master completed (commit 79bbf82aae by @jimklimov)

[AppVeyorBot]

✅ Build nut 2.8.5.4672-master completed (commit 98b11c3a70 by @jimklimov)

• artifacts
• A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4672-master.7z