tk5: move mvsMF to 1.4.1 and read its level from /zosmf/info #44

Follow-up to #42 / #43, which did this for the mvsce image.

tk5/Dockerfile pins MVSMF_VERSION=1.3.0, and tk5/setup_tk5.py (the version check) and .github/workflows/tk5.yml (the readiness probe) read the level from /zosmf/test?fn=version. That is correct for 1.3.0. mvsMF 1.4.x registers /zosmf/test in development builds only; a release answers 404 there, so the probe has to move to GET /zosmf/info (zosmf_full_version, fails on a -dev suffix) at the same time as the pin, as #43 did for mvsce.

Two things from mvsMF 1.4.0 the TK5 setup has to account for as well:

• The console service checks READ on FACILITY MVSMF.CONSOLE itself, fail-closed. The TK5 setup needs that profile (RDEFINE, PERMIT READ to the administrator) like setup_mvsce.py has since mvsce: write the mvsMF console route into HTTPPRM0 #41, and the setup check should assert 401 without a login and 200 with one on /zosmf/restconsoles/v1/log.
• Without profiles in the RAKF class JESSPOOL every user sees only its own jobs. The mvsce image deliberately defines none, because the FTPD and mvsMF suites that test the class require a clean PROFILES; the same decision applies here unless the TK5 image has a different purpose.

The repository has no milestones; none set.