Check versions for dab branches in app repos

All respective changes have been backported from master to dab

No. Only apps that were there already. Nothing new.

 Should we add the agl-service-gps, agl-service-geofence, and agl-service-geoclue to dab? Not hard to do but no applications are currently consuming those binder services.

Also was looking through the applications today to figure which patches should be backported from eel to dab. Most were straightforward, but iot.bzh should look at the low-level-can-service to see which patchsets need to be backported. Since it isn't clear which are important or have already been backported based on commit messages

A lot of applications derive meanwhile from dab in functionality and also new apps are posted (agl-service-geo*) . Some of them do no longer build for dab.

To properly build applications for the release branches, we need to use the branches for apps to.

Most of them were already put in place during the dab release procedures. But these need a cross-check and cherry-pick if they're at the desired state.

End goal is: app repos should have 'dab' branches that are buildable with the dab SDK.   The corresponding CI jobs with triggers for the dab branch will be put in place for that.