Pull a developement branch for activities on T-API 2.4

As T-API 2.4 and 2.1 models can not cohabitate, as soon as the Potassium branch becomes available (after Argon has been released), evaluate the necessity of creating a branch dedicated to T-API 2.4 development (we may not want to de-activate the tapi feature (2.1) on the master branch) for the migration of T-API code to 2.4. If this is the case, create this branch so that we can migrate to T-API 2.4 (existing code + PCE link and Node classes)