As shown in DM-24610, Jenkinsfile for ts_MTAOS can be reorganized to properly build all dependencies.

I believe it's feasible to push that a bit futher, and run from Jenkinsfile:

• build a container required for ts_MTAOS from Dockerfile checkout from ts_Dockerfiles repo
• use the container to run tests for MTAOS
• use the container to run on two nodes client and server (simulated), verifying sal functionality
• push the container to docker hub, if build on tagged commit

This will significantly reduce the efforts needed during integration, and put away problems of remembering steps needed to be performed for a build.