core-TF must manage the version of more selenium-sub-modules

Underlying reason:
In subscription-service-admin-ui - we have a spring-boot-app (SB). SB also contains a BOM of selenium (transiently). 
If subscription-service-admin-ui utilizes a selenium-module, for which we didn't manage the version in test-framework, then the selenium-BOM provided by SB kicks in. This we must avoid