Added conditions for branched services

[adedamola-sode]

Added support for multiple synoptic beamlines.

• Added conditional in find-dirs in main.py to handle branches whose naming in the techui.yaml start with j/k
• Changed synoptic_dir to be abs_path.parent

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.27%. Comparing base (bcf6738) to head (3dfa638).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #214      +/-   ##
==========================================
+ Coverage   96.25%   96.27%   +0.01%     
==========================================
  Files          13       13              
  Lines         962      966       +4     
==========================================
+ Hits          926      930       +4     
  Misses         36       36              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[OCopping]

Are you able to add a test-case for this new logic please?

[niamhdougan]

Please could you add some info of how branched beamlines should be structured moving forward? e.g. BL15I-synoptic and BL15J-synoptic or does everything get put inside synoptic etc?

[adedamola-sode]

@niamhdougan , sorry, I am just now seeing this.

Basically, I based it off the current i15-services repository. Currently, in i15-services, there exists a services directory where the services could either be bl15j, or bl15i. So I have based the screen generation and validation on the difference in the synoptic directory, where the techui.yaml file, could either be a bl15i, or bl15j, or k yaml ( it's contents i.e, beamline, location, e.t.c.) file. Based off what the techui-yaml file says, it looks for the corresponding services in the services folder.

So basically, there will be one i15-services, but for each branch beamline, there will be seperate techui.yaml files. It will be named synoptic but the techui.yaml file will change, we can also keep multiple techui.yaml files in the same synoptic directory, as we reference the chosen one when building the screens.

EDIT: Since the top level index.bob will live in the synoptic folder, causing duplicates/overwriting for multiple techui.yamls in one synoptic folder, the synoptic folder will have to be slit for synoptic-i, synoptic-j etc.

[adedamola-sode]

If there's a synoptic-i, and then a synoptic-j... We will end up duplicating the techui-support folder, I propose for branched beamlines like this, the techui-support folder is symlinked