chore(web): integrates predictive-text builds to top level script, reconnects headless tests

[jahorton]

The main reason I started this PR was the fact that web/build.sh build:engine/predictive-text had absolutely no effect. Calling it when an older version of predictive-text existed on my filesystem would not update it; I had to drill-down into the child projects to get them rebuilt.

I also discovered that web's headless test suite was left disconnected for some reason. This seems to have been done at some point within the 18.0 filesystem reorganization, but was never undone. I believe things should be stable enough to reconnect them now.

For the third commit, the reorg has placed things in such a manner that it... kind of makes sense to have a web/build.sh test actually trigger them. We do still have the two separate build configurations though, so this probably shouldn't happen when doing CI testing - the third commit prevents it, but only in CI mode.

@keymanapp-test-bot skip

[keymanapp-test-bot]

User Test Results

Test specification and instructions

User tests are not required

[ermshiperete]

LGTM, but what's the reason for treating CI and local builds differently (except for the --ci flag)?

A cursory look suggests that predictive-text/worker-main/unit_tests/test.sh test:libraries (which is called by CI) runs the same tests as allowing test runs of the child projects in predictive-text/build.sh. I'd prefer if both CI and local builds would follow the same flow, i.e. running the child actions in predictive-text/build.sh.

[jahorton]

LGTM, but what's the reason for treating CI and local builds differently (except for the --ci flag)?

A cursory look suggests that predictive-text/worker-main/unit_tests/test.sh test:libraries (which is called by CI) runs the same tests as allowing test runs of the child projects in predictive-text/build.sh. I'd prefer if both CI and local builds would follow the same flow, i.e. running the child actions in predictive-text/build.sh.

The only reason I did this is because we have two separate CI configurations for them. After all, they used to be in vastly different sections of the repository.

If we dropped the separate predictive-text CI configuration, I'd drop the unit_tests/test.sh script and call via the child projects. We haven't dropped it (to my knowledge), and I don't wish to break that configuration at this time - that's something we should discuss as a team first.