refactor: Introduce tapir on Pekko DEV-2806

[seakayone]

Migrate all public ProjectEndpoints to Tapir

Pull Request Checklist

Task Description/Number

Issue Number: DEV-

Basic Requirements

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• fix: represents bug fixes
• refactor: represents production code refactoring
• feat: represents a new feature
• docs: documentation changes (no production code change)
• chore: maintenance tasks (no production code change)
• test: all about tests: adding, refactoring tests (no production code change)
• other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No
• Maybe (not 100% sure => check with FE)

Does this PR change client-test-data?

• Yes (don't forget to update the JS-LIB team about the change)
• No

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (12402f3) 18.00% compared to head (e721bc4) 88.10%.
Report is 83 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2870       +/-   ##
===========================================
+ Coverage   18.00%   88.10%   +70.10%     
===========================================
  Files         281      252       -29     
  Lines       28899    23257     -5642     
===========================================
+ Hits         5202    20491    +15289     
+ Misses      23697     2766    -20931     

see 237 files with indirect coverage changes

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

[BalduinLandolt]

Let's wait and see what the outcome of our discussion on the topic will be. But as it stands, looks good to me

[mpro7]

One minor improvement which can be omitted:

[linear]

DEV-2806 Introduce tapi in dsp-api