Only run "Debug Client" workflow on dev-2.x branch

[t2gran]

Summary

This action is run today in entur downstream fork when someone changes a file under /client/**. The action is aborted, but it clutter up the list of run actions. I am not an expert on workflows, but I chaned it slightly so the trigger now filter on both path and branch for pushes. This also make the script a bit cleaner, since the branch filter does not need to be repeated in the run section.

Note! If you use dev-2.x in the fork as a active branch the this PR will not prevent this workflow from running, as @optionsome mentions in a comment below.

Issue

🟥 There is no issue for this.

Unit tests

🟥 This is CI config change, we do not have tests for this.

Documentation

🟥 I have not changed/added doc.

Changelog

🟥 Not relevant

Bumping the serialization version id

🟥 There is no changes to the OTP code.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.84%. Comparing base (5ab75af) to head (6e5a95a).
Report is 122 commits behind head on dev-2.x.

Additional details and impacted files

@@              Coverage Diff              @@
##             dev-2.x    #6402      +/-   ##
=============================================
+ Coverage      69.73%   69.84%   +0.10%     
- Complexity     18023    18123     +100     
=============================================
  Files           2057     2069      +12     
  Lines          76978    77268     +290     
  Branches        7845     7855      +10     
=============================================
+ Hits           53678    53964     +286     
+ Misses         20550    20547       -3     
- Partials        2750     2757       +7     

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

[optionsome]

The title is slightly misleading as this only prevents the workflow being run in a fork if the fork doesn't use the same branch naming convention as upstream. Unfortunately I don't think there is a way to define on which repositories the action should run on (apart from the repository owner check that we already do here but with that solution the workflow still starts but is then aborted).

[t2gran]

In general I would recommend using a different name to the master/development branch in a fork - to avoid misstakes. For example will git automatically set the upstream repository matching the branch name in some cases. This could lead to pushing changes to the wrong repository.

We reasently switch over pipeline from a fork of HSLs repo to using the main opentripplanner repo and changing the entur release branch from entur_develop to main - this switch was surprisingly easy and fast to do.