[CI] Fix cache resolution and syntax in check binary size workflow

[chahatsagarmain]

Which problem is this PR solving?

• Resolves [CI]: Improper cache resolution and conditional statement handling in check bundle size workflow . #2590

Description of the changes

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.58%. Comparing base (1ee19c2) to head (694298e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2591   +/-   ##
=======================================
  Coverage   96.58%   96.58%           
=======================================
  Files         255      255           
  Lines        7732     7732           
  Branches     1944     1996   +52     
=======================================
  Hits         7468     7468           
  Misses        264      264           

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

[hari45678]

@yurishkuro This PR is creating new cache key on each commit to the main branch. That would result in cache miss on subsequent PRs.

[yurishkuro]

it does create new key, but it uses a pattern-match to find them which picks the latest. Using a fixed key for some reason means cache will not be updated after the first value.

[hari45678]

Yes, but it isn't picking up the latest cache key in this (jaeger-ui) repository, maybe because here exists an exact key match, so it is picking up that stale cache.
For example, in bundle check workflow in this PR #2593, the action is picking up the key jaeger-ui-bundle-size, and not the latest key jaeger-ui-bundle-size-12822565240 which was created with bundle check action trigger with latest push to main branch after this PR was merged.

[yurishkuro]

Then we still don't have a solution

[chahatsagarmain]

@yurishkuro we need to delete the old exact key match , from action -> caches and the new restores should be done from this change .

[hari45678]

@yurishkuro we need to delete the old exact key match , from action -> caches .

yes that should solve this issue

[yurishkuro]

deleted