(e2e): catalog versions e2e weekly tests

[tplevko]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.51%. Comparing base (c28ed6d) to head (194aeb7).
Report is 14 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##               main    #1889    +/-   ##
==========================================
  Coverage     78.51%   78.51%            
  Complexity      367      367            
==========================================
  Files           469      469            
  Lines         14816    14816            
  Branches       2749     2832    +83     
==========================================
  Hits          11633    11633            
+ Misses         3095     2910   -185     
- Partials         88      273   +185     

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[lordrip]

Look goods to me 👍

I just have 2 questions:

1. Is it possible to leave the e2e-tests.yaml file as it was, so by default weekly tests will be ignored? The goal is to have the same experience locally as on the CI
2. Did you had the chance to check if we can use the constant from the @kaoto/camel-catalog package so the catalog versions get updated when updating the catalog?

[tplevko]

1. Is it possible to leave the `e2e-tests.yaml` file as it was, so by default weekly tests will be ignored? The goal is to have the same experience locally as on the CI

The added env: grepTags=-weekly actually makes sure the weekly tests are being ignored in the PR runs. I can add this env variable also to the e2e:headless tag, so we have the same experience when running the tests locally.

2. Did you had the chance to check if we can use the constant from the `@kaoto/camel-catalog` package so the catalog versions get updated when updating the catalog?

I tried to utilize the constant, but wasn't able to use it in the test. I think this won't be a huge issue as the versions change only seldomly and the test can be updated once there is a newer version used.