Decouple influxdb services for production and development

The influxdb database server is currently used by production instance of CI and also for developers to storing their data. We have seen that the influxdb is not scalable and might even crash testresults.qt.io server which runs out of memory because influxdb gets overloaded by data.

If influxdb is unavailable, we cannot see the current state of our CI system or analyse flakiness data, which is critical for providing a good quality of service to our customers and developers.

If testresults.qt.io is unavailable, the whole open source community and our customers cannot access integration logs. That should be avoided at all costs.

The suggestion is to have two influxdb services where the other one serves only CI / Open-Source community and the other one is left for development and testing, which could be even moved to another server (eg. ci-files01-hki.intra.qt.io), which would lower the risk even further.