Verification on Engine Upload shall be integrated and configurable via Admin Client

[BLuedtke]

(Feature Request)

The experimental feature for verification of train engines upon upload shall be integrated into the main branch. With additional functionality: An Admin shall be able to enable or disable whether engines are verified upon upload. An Admin shall be able to do so via a web-interface akin to those existing for drivers and controllers. Furthermore, this shall be possible via the Python client as well.

I'll work on implementing this functionality. I'll do so on the verify_engine_models branch.

[BLuedtke]

Ran some user-tests on the changes in the verify_engine_models branch. Small adjustments were needed, but generally works now. Two issues remaining that I saw:

• When the server has not started up yet, the admin web page verification toggle is set to OFF, as the get-verification query is not answered by the non-running server. However, technically, the server doesn't need to start libbidib etc. before being able to answer get-verification. I'll see if I can adjust the implementation accordingly.
• Loading the client and controller web pages loads the script.js, which in turn queries get-verification. Only the admin page needs get-verification, so it shouldn't be queried when loading the other pages. I'll look for a simple fix.

[eyip002]

What if the verification section of the Admin page is initially a Get Verification Settings button that only reveals the verification settings if the verification server is running?

[BLuedtke]

That would be a valid workaround. Though a single small extra http-get for a page load is not that bad either, so we could leave it as-is. Just need to update/remove the 'running' check in the handler for that get.