Jenkins for CI

[manauref]

BEWARE: I'm not going to merge this into main, i'm going to merge it into agent_tools. I temporarily have it as merging into main so it triggers a an automatic build/test. So please approve when ready but don't merge, i'll do that.

We add the Jenkins file and readme with instructions on how to set up.

Note some terminology:
One may add

• Controllers: a controller is a place CI is launched from. For example, I added a personal computer controller which only runs CI for PRs authored by myself (others can do this too).
• Nodes: this is hardware CI runs on. The hardware where the controller resides is typically a node, but one may also add a remote node (e.g. if I had access to a workstation via ssh, I could add it as a node in my controller).

Currently CI runs on my laptop, but the idea is for us to add a shared workstation as a node (possibly in mine or @JunoRavin 's controller; makes me wonder if two controllers can add the same node), which would run whenever anyone submits a PR to merge into main.

Procedure

Presently the CI system:

1. Builds main, creates accepted results for MOAT reg tests.
2. Checks out the branch to be tested.
3. Runs unit tests.
4. Runs MOAT regression tests and checks.
5. Reports to GitHub if unit and reg tests passed.

If a PR genuinely needs to change the accepted results, one needs to list that test in ci/jenkins/expected_regression_diffs.txt‎.

Lastly, see below and you'll see this PR passes CI run on my laptop. You may not be able to click it (not sure, try), but when I do it opens my local Jenkins page in which I see this

[Antoinehoff]

Hm there is a commit "Co-Authored-By" Claude. I really want to avoid that, they don't deserve to be mentioned.

[manauref]

Hm there is a commit "Co-Authored-By" Claude. I really want to avoid that, they don't deserve to be mentioned.

If we are all tracking stuff with something like Entire, sure. Otherwise I'd prefer to keep it.