Adapt TransportPCE CI to a better usage of lighty build

Currently, lighty build integrates the TAPI functionality per default, because tapi functional tests are embeded inside functional tests of devices 2.2.1 (although logically they should not be specific to devices 221). And yet, in karaf, Tapi is managed as an optional feature.
It would be worth adapting the CI to be able to build lighty without TAPI functionalities activated when not necessary.