Try to fool CI to migrate to Eaton MBT

[aquette]

No description provided.

[jimklimov]

Generally LGTM, when/if CI does pick it up do check that it runs equivalent tests (note the configure options in the old text) to be sure the build scopes are relevant (DMF generated, etc.) or find a way to propagate those into the build. Also the old recipe should have prepared the (partial?) dist tarball pushed for publication to OBS, most notably the generated man pages as a large time hog for the build (especially comparing to negligible time for C sources vs. ccache'd iterations).

UPDATE: Looking at build log, the step used is configuring specifically for zproject-style builds (e.g. --enable-drafts) that NUT is not too similar to. Notably, it uses --enable-Werror unconditionally, and current 42ity NUT codebase fails that (took a over a year of weekends and holidays to clean up the upstream NUT from several layers of warnings, but 42ity fork's unique code still has a lot ahead to reach the bar). So for now, this setting needs to be changed (different step defined in library for NUT builds?)

See also the ci_build.sh and Jenkinsfile-dynamatrix merged from upstream NUT to automate much of such test-building.