change jep dependency from api to implementation

[maximiliankaul]

No need to expose jep's API to CPG users.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.15%. Comparing base (3a430fc) to head (dc6c7d4).
Report is 1 commits behind head on main.

Additional details and impacted files

see 1 file with indirect coverage changes

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[oxisto]

Are you sure about that? If one uses the python frontend, I am pretty sure they need JEP as a dependency and it won't be registered to them as a dependency unless its an api dependency.

[maximiliankaul]

Are you sure about that? If one uses the python frontend, I am pretty sure they need JEP as a dependency and it won't be registered to them as a dependency unless its an api dependency.

No, I'm not at all sure about this entire build system.

• I don't see why the jep API being exposed to the end-user would be of any benefit.
• Test (local and on GitHub) still work just fine.
• Using the CPG stand-alone (say cpg-console) works fine.

If there are any other tests you'd like me to do, then I'm happy for any pointers :)

[oxisto]

Are you sure about that? If one uses the python frontend, I am pretty sure they need JEP as a dependency and it won't be registered to them as a dependency unless its an api dependency.

No, I'm not at all sure about this entire build system.

• I don't see why the jep API being exposed to the end-user would be of any benefit.
• Test (local and on GitHub) still work just fine.
• Using the CPG stand-alone (say cpg-console) works fine.

If there are any other tests you'd like me to do, then I'm happy for any pointers :)

Running from an external project still works. LGTM then